← previous blocknext block →recent activity
Analyzing
Block #83,878,071
15 transactions · 13 stateful · 2026-06-26 19:21:38 UTC
Parallelism
80/100
Blocked
23%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,878,071 · 15 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
1w04w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x7bc6be62…a373
0xd32edf…ff58
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x84d5ab6f…810e
0x065c9d…c394
2 touches
0 conflicts
0xa53d1032…9e1d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0018
0x1b6862…e19c
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 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity