← previous blocknext block →recent activity
Analyzing
Block #86,969,440
24 transactions · 21 stateful · 2026-07-11 03:03:29 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,969,440 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w06w18w09w112w014w015w118w219w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4981d48d…e2ef
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0xcd31c7ae…4417
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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
3 conflicts on slot 0x4981d48d3a…00e2ef
Audit this contract →
← previous block·next block →recent activity