← previous blocknext block →recent activity
Analyzing
Block #96,481,485
6 transactions · 5 stateful · 2026-08-16 11:46:29 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,481,485 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d8721c7…d7f5
0x34b655…2a6f
4 touches
1 conflict
0x4cd46947…fbd9
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9054
0x34b655…2a6f
2 touches
0 conflicts
0x1a2055c7…9055
0x34b655…2a6f
2 touches
0 conflicts
0x21280422…0930
0x34b655…2a6f
2 touches
0 conflicts
0x67a56c8b…f955
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
1 conflict on slot 0x4d8721c73d…add7f5
Audit this contract →
← previous block·next block →recent activity