← previous blocknext block →recent activity
Analyzing
Block #96,579,386
11 transactions · 9 stateful · 2026-08-16 19:59:10 UTC
Parallelism
73/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,579,386 · 11 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
1w02w16w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6457c2d…76d7
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x2cdc755d…f277
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x785705a8…33e5
0x34b655…2a6f
6 touches
3 conflicts
0x80884f59…ac94
0x34b655…2a6f
5 touches
3 conflicts
0x032ec3de…2902
0x34b655…2a6f
5 touches
3 conflicts
0x24b08f9c…e594
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
3 conflicts on slot 0xc6457c2dbf…a976d7
Audit this contract →
← previous block·next block →recent activity