← previous blocknext block →recent activity
Analyzing
Block #83,194,859
14 transactions · 9 stateful · 2026-06-23 15:20:46 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,194,859 · 14 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
0x2886e2bc…6ab8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x042d0151…a098
0x065c9d…c394
2 touches
0 conflicts
0x0b8f560d…b00f
0x065c9d…c394
2 touches
0 conflicts
0x186d26f7…9108
0x065c9d…c394
2 touches
0 conflicts
0x1a1e2af3…088d
0x065c9d…c394
2 touches
0 conflicts
0x1eab98ab…307f
0x065c9d…c394
2 touches
0 conflicts
0x700d80da…8a8f
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 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity