← previous blocknext block →recent activity
Analyzing
Block #96,666,015
10 transactions · 8 stateful · 2026-08-17 03:14:53 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,666,015 · 10 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
2w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xb0608dfe…083d
0x34b655…2a6f
4 touches
1 conflict
0x890a1db9…1712
0xa6afd3…d132
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x369883e3…a449
0x34b655…2a6f
2 touches
0 conflicts
0x4cb450ac…4047
0x34b655…2a6f
2 touches
0 conflicts
0x4e621c19…6089
0x34b655…2a6f
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 0xd6113c0f7f…b30a4b
Audit this contract →
← previous block·next block →recent activity