← previous blocknext block →recent activity
Analyzing
Block #86,085,498
14 transactions · 11 stateful · 2026-07-07 00:35:17 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,085,498 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0xfb5eea3e…7324
0x065c9d…c394
4 touches
1 conflict
0x7d011a90…9e81
0x065c9d…c394
3 touches
1 conflict
0x06636560…5ad6
0x065c9d…c394
3 touches
1 conflict
0xbbd859e3…127f
0x065c9d…c394
3 touches
1 conflict
0xbbfc1389…94c7
0x065c9d…c394
3 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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity