← previous blocknext block →recent activity
Analyzing
Block #96,045,594
11 transactions · 11 stateful · 2026-08-14 23:14:07 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,045,594 · 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
3w04w05w17w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x168f7615…a8dd
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2c8f52ce…fe9a
0x34b655…2a6f
6 touches
3 conflicts
0xd56d737c…11ad
0x34b655…2a6f
5 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x31616f97…1acc
0x34b655…2a6f
4 touches
1 conflict
0x4d5053d1…3b7d
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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 0x168f7615e7…68a8dd
Audit this contract →
← previous block·next block →recent activity