← previous blocknext block →recent activity
Analyzing
Block #83,862,401
33 transactions · 27 stateful · 2026-06-26 17:37:02 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,862,401 · 33 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w411w514w115w016w117w018w121w624w025w129w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
10 touches
10 conflicts
0xabbcbdf8…104e
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
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 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity