← previous blocknext block →recent activity
Analyzing
Block #86,712,928
17 transactions · 17 stateful · 2026-07-09 22:29:01 UTC
Parallelism
82/100
Blocked
24%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,712,928 · 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
2w03w17w08w19w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x813d6148…7e8f
0x34b655…2a6f
6 touches
3 conflicts
0x034d14da…9f5f
0x34b655…2a6f
4 touches
1 conflict
0x17fbe072…2ea6
0x34b655…2a6f
4 touches
1 conflict
0x1e4391d6…03ac
0x34b655…2a6f
4 touches
1 conflict
0x2ff44d76…33d6
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x69c491e3…98d9
0x34b655…2a6f
4 touches
1 conflict
0x7139bf32…c881
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 0x813d614820…4f7e8f
Audit this contract →
← previous block·next block →recent activity