← previous blocknext block →recent activity
Analyzing
Block #86,051,884
13 transactions · 12 stateful · 2026-07-06 20:51:12 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #86,051,884 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xfe58e817…2536
0x065c9d…c394
3 touches
1 conflict
0x192c9fb6…e3a6
0x065c9d…c394
3 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
2 touches
0 conflicts
0x99269aa2…2c25
0x065c9d…c394
2 touches
0 conflicts
0xc41507a8…39f7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity