← previous blocknext block →recent activity
Analyzing
Block #96,536,514
21 transactions · 17 stateful · 2026-08-16 16:23:33 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,536,514 · 21 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
1w02w14w25w36w48w213w514w618w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f900be0…cd6e
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x32a1a68b…8ee4
0x34b655…2a6f
6 touches
3 conflicts
0xd253247a…5d1f
0x34b655…2a6f
6 touches
3 conflicts
0x4fa49ab2…3116
0x34b655…2a6f
6 touches
3 conflicts
0x6aa624fd…a850
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1c8356f1…c7a2
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
10 conflicts on slot 0x6f900be04d…4ccd6e
Audit this contract →
← previous block·next block →recent activity