← previous blocknext block →recent activity
Analyzing
Block #83,467,837
21 transactions · 18 stateful · 2026-06-24 21:44:28 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,467,837 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w08w39w010w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 conflicts
0x29e9436e…b940
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x659bd0…a9da
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x7e28e55c…d05c
0x754704…b603
4 touches
1 conflict
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
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 0x2886e2bc57…316ab8
Audit this contract →
← previous block·next block →recent activity