← previous blocknext block →recent activity
Analyzing
Block #83,867,894
11 transactions · 11 stateful · 2026-06-26 18:13:46 UTC
Parallelism
82/100
Blocked
9%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,867,894 · 11 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x1ecfd898…f68f
0x065c9d…c394
2 touches
1 conflict
0xaec06d75…a2f5
0x065c9d…c394
2 touches
1 conflict
0x465294dc…0ff6
0x065c9d…c394
2 touches
0 conflicts
0x6d8e8e3c…2c07
0x065c9d…c394
2 touches
0 conflicts
0x93937aa7…8788
0x065c9d…c394
2 touches
0 conflicts
0xbecf17c5…d2d9
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