← previous blocknext block →recent activity
Analyzing
Block #96,534,285
18 transactions · 14 stateful · 2026-08-16 16:12:20 UTC
Parallelism
61/100
Blocked
57%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,534,285 · 18 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
2w03w16w19w010w211w312w414w515w616w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a3e0d2e…4f3b
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa0d3a786…91d9
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
6 touches
3 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
6 touches
3 conflicts
0x9b2d3bee…8eec
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 0x1a3e0d2e8b…174f3b
Audit this contract →
← previous block·next block →recent activity