← previous blocknext block →recent activity
Analyzing
Block #86,331,922
17 transactions · 16 stateful · 2026-07-08 04:00:37 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,331,922 · 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
2w03w14w05w08w111w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71641e8d…a781
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9417
0x34b655…2a6f
4 touches
1 conflict
0xe983d809…501e
0x34b655…2a6f
4 touches
1 conflict
0xec0e0220…cb90
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xdef13815…97bc
0x065c9d…c394
4 touches
1 conflict
0x034f1f86…4e8d
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
1 conflict on slot 0x71641e8d03…e8a781
Audit this contract →
← previous block·next block →recent activity