← previous blocknext block →recent activity
Analyzing
Block #86,843,908
30 transactions · 25 stateful · 2026-07-10 13:04:21 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,843,908 · 30 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
1w02w03w14w26w17w08w19w213w214w315w317w419w520w121w222w426w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7babfe9a…ff96
0x34b655…2a6f
8 touches
6 conflicts
0x33bd5ec4…af53
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xfaef08b1…0696
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
6 conflicts on slot 0x7babfe9a22…93ff96
Audit this contract →
← previous block·next block →recent activity