← previous blocknext block →recent activity
Analyzing
Block #96,665,023
9 transactions · 8 stateful · 2026-08-17 03:09:54 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,665,023 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x0a8f8b9c…3046
0x34b655…2a6f
4 touches
1 conflict
0x458b9085…9ee2
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe2ca9bf2…8da8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x367b69ad60…4333d9
Audit this contract →
← previous block·next block →recent activity