← previous blocknext block →recent activity
Analyzing
Block #96,219,535
11 transactions · 10 stateful · 2026-08-15 13:48:59 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,219,535 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x524f0872…0d12
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x2b2cf495…1c6f
0x34b655…2a6f
4 touches
1 conflict
0x425376d1…8979
0x34b655…2a6f
4 touches
1 conflict
0x45b3c66c…b788
0x34b655…2a6f
4 touches
1 conflict
0x4638d837…130f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6939e474…4256
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 0x524f087203…e70d12
Audit this contract →
← previous block·next block →recent activity