← previous blocknext block →recent activity
Analyzing
Block #96,581,650
14 transactions · 9 stateful · 2026-08-16 20:10:33 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,581,650 · 14 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
1w05w06w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36cb2e…0929
0x34b655…2a6f
4 touches
1 conflict
0xa195321d…46ec
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0x1b2a2bb5…243d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xcd1f9150…430f
0x34b655…2a6f
4 touches
1 conflict
0xf481d314…3fdd
0x34b655…2a6f
4 touches
1 conflict
0x39cad37a…f229
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 0x9a36cb2e52…470929
Audit this contract →
← previous block·next block →recent activity