← previous blocknext block →recent activity
Analyzing
Block #86,494,836
17 transactions · 13 stateful · 2026-07-08 22:09:20 UTC
Parallelism
88/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,494,836 · 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
1w02w14w05w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f35c56f…046b
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0xa3c36de0…3cf3
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0dd44476…ef40
0x34b655…2a6f
4 touches
1 conflict
0x3a9f49b6…6f47
0x40c49f…2af0
2 touches
0 conflicts
0xa71a5965…7227
0x40c49f…2af0
2 touches
0 conflicts
0xd63c3642…9a98
0x40c49f…2af0
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 0x2f35c56f7b…bd046b
Audit this contract →
← previous block·next block →recent activity