← previous blocknext block →recent activity
Analyzing
Block #86,485,644
13 transactions · 12 stateful · 2026-07-08 21:07:57 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,485,644 · 13 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
4w05w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x80513e49…5a6a
0x34b655…2a6f
4 touches
1 conflict
0x0e9a70ab…e67c
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe727ab72…768b
0x34b655…2a6f
4 touches
1 conflict
0xebd8c9b0…2ba6
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x3d4584df…ffed
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 0x7ee6007b44…92fd68
Audit this contract →
← previous block·next block →recent activity