← previous blocknext block →recent activity
Analyzing
Block #86,501,016
21 transactions · 19 stateful · 2026-07-08 22:50:32 UTC
Parallelism
90/100
Blocked
16%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,501,016 · 21 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
1w03w04w19w117w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba62c547…57a1
0x065c9d…c394
4 touches
1 conflict
0xd3f3fd24…10c6
0x065c9d…c394
3 touches
1 conflict
0x58e4cc94…91cc
0x065c9d…c394
3 touches
1 conflict
0x5c54f4f8…6cf7
0x065c9d…c394
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 0x52e6914362…6e95ad
Audit this contract →
← previous block·next block →recent activity