← previous blocknext block →recent activity
Analyzing
Block #86,364,784
13 transactions · 10 stateful · 2026-07-08 07:39:53 UTC
Parallelism
69/100
Blocked
30%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,364,784 · 13 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
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x18cf3003…51d1
0x065c9d…c394
6 touches
3 conflicts
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x233d0beb…86d5
0x065c9d…c394
2 touches
0 conflicts
0x2e6ff717…dc93
0x065c9d…c394
2 touches
0 conflicts
0x4ac2d82e…e356
0x065c9d…c394
2 touches
0 conflicts
0xc2e13187…104d
0x065c9d…c394
2 touches
0 conflicts
0xe6f4a326…ec4f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity