← previous blocknext block →recent activity
Analyzing
Block #96,654,522
11 transactions · 10 stateful · 2026-08-17 02:17:05 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,654,522 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x116bfb72…528f
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x6eb3e5af…064e
0x34b655…2a6f
4 touches
1 conflict
0x9a89094e…f5b2
0x34b655…2a6f
4 touches
1 conflict
0x17935a8f…a796
0x34b655…2a6f
4 touches
1 conflict
0x1d68c976…b6e6
0x34b655…2a6f
4 touches
1 conflict
0xadd9c687…1f8b
0x34b655…2a6f
4 touches
1 conflict
0xc6db063e…292e
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 0x116bfb72b7…ca528f
Audit this contract →
← previous block·next block →recent activity