← previous blocknext block →recent activity
Analyzing
Block #83,468,309
17 transactions · 16 stateful · 2026-06-24 21:47:38 UTC
Parallelism
82/100
Blocked
19%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,468,309 · 17 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
1w02w03w15w06w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x3387fdbc…ff9e
0x065c9d…c394
2 touches
0 conflicts
0x353aeba9…0a69
0x065c9d…c394
2 touches
0 conflicts
0xa3fff06a…9d38
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity