← previous blocknext block →recent activity
Analyzing
Block #96,556,976
16 transactions · 14 stateful · 2026-08-16 18:06:27 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.94
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,556,976 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x2d5e2e86…5fcd
0x34b655…2a6f
4 touches
1 conflict
0x3e8c516d…4c8f
0x34b655…2a6f
4 touches
1 conflict
0x4c54d22c…305e
0x34b655…2a6f
4 touches
1 conflict
0x6280c6c6…11ac
0x34b655…2a6f
4 touches
1 conflict
0x6a10a152…a08f
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
28 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity