← previous blocknext block →recent activity
Analyzing
Block #96,435,073
19 transactions · 18 stateful · 2026-08-16 07:53:01 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,435,073 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w18w29w210w311w412w214w318w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x81da6711…3869
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity