← previous blocknext block →recent activity
Analyzing
Block #83,862,799
13 transactions · 12 stateful · 2026-06-26 17:39:42 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,862,799 · 13 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0xc3c8642a…7da5
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xae351b5e…4a9a
0x065c9d…c394
3 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x2e24614d…aa8b
0x5afd3e…7620
2 touches
0 conflicts
0x3f3a4b15…dc80
0x5afd3e…7620
2 touches
0 conflicts
0x6da99c93…acb2
0x5afd3e…7620
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 0x0b16149e0d…887d4d
Audit this contract →
← previous block·next block →recent activity