← previous blocknext block →recent activity
Analyzing
Block #96,621,494
12 transactions · 11 stateful · 2026-08-16 23:30:58 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,621,494 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9f9800f…38fa
0x34b655…2a6f
4 touches
1 conflict
0x35c68080…aace
0x851145…3f07
4 touches
1 conflict
0xc9327614…ba36
0x851145…3f07
4 touches
1 conflict
0xd6265424…0d3a
0x851145…3f07
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b44
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
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
1 conflict on slot 0xf9f9800fa8…6638fa
Audit this contract →
← previous block·next block →recent activity