← previous blocknext block →recent activity
Analyzing
Block #96,797,722
9 transactions · 8 stateful · 2026-08-17 14:17:19 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,797,722 · 9 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
1w04w05w16w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xbf7ad54e…ec12
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x0bc80bb4…a97c
0x851145…3f07
4 touches
1 conflict
0x62811193…1867
0x2b46c0…1669
2 touches
0 conflicts
0x62811193…1868
0x2b46c0…1669
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 0x0672e4a279…2f8d1f
Audit this contract →
← previous block·next block →recent activity