← previous blocknext block →recent activity
Analyzing
Block #83,193,402
23 transactions · 17 stateful · 2026-06-23 15:11:01 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,193,402 · 23 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
2w03w04w16w08w211w112w313w414w016w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x731e6d82…2883
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x12449f39…46a6
0xd32edf…ff58
7 touches
6 conflicts
0x2886e2bc…6ab8
0x065c9d…c394
6 touches
3 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
10 conflicts on slot 0x731e6d8269…072883
Audit this contract →
← previous block·next block →recent activity