← previous blocknext block →recent activity
Analyzing
Block #96,596,979
11 transactions · 8 stateful · 2026-08-16 21:27:40 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,596,979 · 11 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w15w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa55f66c8…be88
0x34b655…2a6f
6 touches
3 conflicts
0x2577a4d2…07d4
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x5060cdde…445d
0x34b655…2a6f
4 touches
1 conflict
0xf2f40f08…5cdb
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xa55f66c8c9…5cbe88
Audit this contract →
← previous block·next block →recent activity