← previous blocknext block →recent activity
Analyzing
Block #96,266,264
8 transactions · 7 stateful · 2026-08-15 17:44:01 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,266,264 · 8 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
2w03w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc2356ec…27e5
0x34b655…2a6f
4 touches
1 conflict
0x19b34ad0…1b7b
0x34b655…2a6f
4 touches
1 conflict
0x19b34ad0…1b7c
0x34b655…2a6f
4 touches
1 conflict
0x5ea47b59…c8bb
0x34b655…2a6f
4 touches
1 conflict
0x63a6dacd…54a1
0x34b655…2a6f
4 touches
1 conflict
0x6b17f7a0…af41
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
1 conflict on slot 0xdc2356ecfa…0f27e5
Audit this contract →
← previous block·next block →recent activity