← previous blocknext block →recent activity
Analyzing
Block #86,736,955
13 transactions · 11 stateful · 2026-07-10 01:09:35 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,736,955 · 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
2w07w08w19w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4b8c5b1…836b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa08f40b2…9a93
0x34b655…2a6f
4 touches
1 conflict
0xb448b3f9…fdb9
0x34b655…2a6f
4 touches
1 conflict
0x06aed19e…ca57
0x34b655…2a6f
2 touches
0 conflicts
0x091cc84a…50c1
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…00a6
0xbb4738…ed6c
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 0xb4b8c5b109…eb836b
Audit this contract →
← previous block·next block →recent activity