← previous blocknext block →recent activity
Analyzing
Block #86,363,850
13 transactions · 12 stateful · 2026-07-08 07:33:40 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,363,850 · 13 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x07e8f365…3ea7
0x065c9d…c394
2 touches
0 conflicts
0x49130a82…0ab0
0x065c9d…c394
2 touches
0 conflicts
0x4c08ce3a…fe99
0x065c9d…c394
2 touches
0 conflicts
0x5d2756dc…42a0
0x065c9d…c394
2 touches
0 conflicts
0xaa78dc11…c0dd
0x065c9d…c394
2 touches
0 conflicts
0xd2b761d1…6ad8
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 0xcc8faac238…88c766
Audit this contract →
← previous block·next block →recent activity