← previous blocknext block →recent activity
Analyzing
Block #83,481,140
16 transactions · 13 stateful · 2026-06-24 23:13:13 UTC
Parallelism
81/100
Blocked
15%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,481,140 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x078b6829…2b22
0x065c9d…c394
2 touches
0 conflicts
0x07d78819…4c48
0x065c9d…c394
2 touches
0 conflicts
0x4044aeba…dd52
0x065c9d…c394
2 touches
0 conflicts
0x67fba330…b815
0x065c9d…c394
2 touches
0 conflicts
0x98e28a3e…2673
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity