← previous blocknext block →recent activity
Analyzing
Block #86,445,642
22 transactions · 16 stateful · 2026-07-08 16:40:17 UTC
Parallelism
91/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,445,642 · 22 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
1w05w06w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x32e307c4…0e10
0x065c9d…c394
4 touches
1 conflict
0x6c4b2d4c…bb3e
0x065c9d…c394
3 touches
1 conflict
0x3109b1ee…23ed
0x065c9d…c394
3 touches
1 conflict
0x3ac9f70f…45cf
0x065c9d…c394
3 touches
1 conflict
0x59bd93e7…de35
0x065c9d…c394
3 touches
1 conflict
0x49cbdb1b…bda4
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity