← previous blocknext block →recent activity
Analyzing
Block #84,425,914
10 transactions · 9 stateful · 2026-06-29 08:11:36 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,425,914 · 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
2w04w05w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ba673e3…6689
0x065c9d…c394
4 touches
1 conflict
0xa0592331…1e7f
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x17aabe64…4a4b
0x065c9d…c394
4 touches
1 conflict
0x19bfb0e5…73b4
0x34b655…2a6f
2 touches
0 conflicts
0x1d6cb721…c88c
0x34b655…2a6f
2 touches
0 conflicts
0x2943be3a…1347
0x34b655…2a6f
2 touches
0 conflicts
0x3768c162…4cb6
0x34b655…2a6f
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 0x7ba673e3b0…8a6689
Audit this contract →
← previous block·next block →recent activity