← previous blocknext block →recent activity
Analyzing
Block #96,612,383
10 transactions · 9 stateful · 2026-08-16 22:45:09 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.3
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,612,383 · 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
1w02w14w05w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ae9c44b…e801
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1e58bae1…9157
0x34b655…2a6f
2 touches
0 conflicts
0x2e4ef777…70ba
0x34b655…2a6f
2 touches
0 conflicts
0x325d8ae4…fac6
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 0x1ae9c44b51…65e801
Audit this contract →
← previous block·next block →recent activity