← previous blocknext block →recent activity
Analyzing
Block #96,609,820
13 transactions · 13 stateful · 2026-08-16 22:32:16 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,609,820 · 13 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
3w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28e5dbea…2f7f
0x34b655…2a6f
4 touches
1 conflict
0x44a35e35…6dcf
0x34b655…2a6f
4 touches
1 conflict
0x5376f5ee…5daa
0x34b655…2a6f
4 touches
1 conflict
0x1e4ffaec…3966
0x34b655…2a6f
4 touches
1 conflict
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x711fd7bf…dd7d
0x065c9d…c394
2 touches
0 conflicts
0x94b1f725…b27f
0x065c9d…c394
2 touches
0 conflicts
0x99a3d7b6…591e
0x065c9d…c394
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 0x28e5dbeae9…ae2f7f
Audit this contract →
← previous block·next block →recent activity