← previous blocknext block →recent activity
Analyzing
Block #86,960,452
17 transactions · 16 stateful · 2026-07-11 02:03:22 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,960,452 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0xd3eb9e87…7962
0xd32edf…ff58
3 touches
1 conflict
0x07e75ab9…2097
0x065c9d…c394
2 touches
0 conflicts
0x171ecc5e…111b
0x065c9d…c394
2 touches
0 conflicts
0x33ead0ff…a24e
0x065c9d…c394
2 touches
0 conflicts
0x49cbdb1b…bda4
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
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity