← previous blocknext block →recent activity
Analyzing
Block #83,494,135
10 transactions · 9 stateful · 2026-06-25 00:39:48 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,494,135 · 10 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
1w03w1
- 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
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x017ae08a…65dd
0x065c9d…c394
2 touches
0 conflicts
0x0c8c031e…f90b
0x065c9d…c394
2 touches
0 conflicts
0x4428c745…95d2
0x065c9d…c394
2 touches
0 conflicts
0x47d3f6c2…c7f0
0x065c9d…c394
2 touches
0 conflicts
0x7a6f8193…9dc1
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