← previous blocknext block →recent activity
Analyzing
Block #96,609,416
19 transactions · 18 stateful · 2026-08-16 22:30:14 UTC
Parallelism
63/100
Blocked
39%
Avg conflicts / tx
1.11
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,609,416 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w37w410w514w118w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xd58e5c6b…7188
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xc6225eed…dcd6
0x34b655…2a6f
6 touches
3 conflicts
0xc9327614…ba36
0x851145…3f07
4 touches
1 conflict
0x3d6c26e5…1b45
0x34b655…2a6f
4 touches
1 conflict
0x90b56fb4…ae7b
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
15 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity