← previous blocknext block →recent activity
Analyzing
Block #86,258,469
17 transactions · 15 stateful · 2026-07-07 19:50:15 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,258,469 · 17 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
2w03w14w25w06w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x7b87b19f…ae1b
0x065c9d…c394
2 touches
0 conflicts
0xa114bb16…3efa
0x065c9d…c394
2 touches
0 conflicts
0xa7640566…6a02
0x065c9d…c394
2 touches
0 conflicts
0xb396404f…87f6
0x065c9d…c394
2 touches
0 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
3 conflicts on slot 0x0efc210ee8…0e70ab
Audit this contract →
← previous block·next block →recent activity