← previous blocknext block →recent activity
Analyzing
Block #86,137,394
17 transactions · 13 stateful · 2026-07-07 06:21:44 UTC
Parallelism
88/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,137,394 · 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
6w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x390a7475…212b
0x065c9d…c394
4 touches
1 conflict
0x6e3d1028…e8e8
0x065c9d…c394
3 touches
1 conflict
0xb235d2e8…35d2
0x065c9d…c394
3 touches
1 conflict
0xa0bab64e…b8c0
0x080ec9…fe74
2 touches
0 conflicts
0x00000000…0008
0x14c8e4…fdcb
2 touches
0 conflicts
0x00000000…0009
0x14c8e4…fdcb
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity