← previous blocknext block →recent activity
Analyzing
Block #86,954,807
10 transactions · 9 stateful · 2026-07-11 01:25:37 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,954,807 · 10 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
2w03w14w26w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0xefcaccf2…c083
0x34b655…2a6f
4 touches
1 conflict
0xf5042875…9a93
0x34b655…2a6f
4 touches
1 conflict
0xf96f1cdc…d66e
0x34b655…2a6f
4 touches
1 conflict
0xfcdb5918…2b49
0x34b655…2a6f
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity