← previous blocknext block →recent activity
Analyzing
Block #96,494,847
7 transactions · 4 stateful · 2026-08-16 12:53:41 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,494,847 · 7 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
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e1f5171…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0xcf59d5c4…7b64
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x57f6d07d…c33b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x1d39a8f0…a833
0x34b655…2a6f
2 touches
0 conflicts
0x3d2e7bcf…54f9
0x34b655…2a6f
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 0x2e1f517172…84ad2d
Audit this contract →
← previous block·next block →recent activity