← previous blocknext block →recent activity
Analyzing
Block #86,656,010
18 transactions · 17 stateful · 2026-07-09 16:09:12 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,656,010 · 18 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
1w02w13w06w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2fa7755…4c09
0x34b655…2a6f
4 touches
1 conflict
0xdc9c727c…6841
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x6c68ddc9…d106
0xb1dbf0…c0d3
4 touches
1 conflict
0x7f430e47…4cbd
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a8
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1a9
0xb1dbf0…c0d3
4 touches
1 conflict
0x8590b692…b267
0x34b655…2a6f
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 0xb2fa77553e…f84c09
Audit this contract →
← previous block·next block →recent activity