← previous blocknext block →recent activity
Analyzing
Block #83,659,686
14 transactions · 13 stateful · 2026-06-25 19:04:30 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,659,686 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
6 touches
3 conflicts
0x912e4494…3849
0x065c9d…c394
6 touches
3 conflicts
0x9b0686b5…f28b
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x0d5ae0d1…7674
0x010592…1c83
2 touches
0 conflicts
0xe0220ff1…563d
0x010592…1c83
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: MarginAccount
3 conflicts on slot 0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block·next block →recent activity