← previous blocknext block →recent activity
Analyzing
Block #84,489,676
12 transactions · 11 stateful · 2026-06-29 15:16:47 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,489,676 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x003e3399…a0a5
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x344dbdb0…0cc0
0x34b655…2a6f
2 touches
0 conflicts
0xac206e47…ef7d
0x34b655…2a6f
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x7a7fc8dc…fd4d
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 0xe75cebb6e9…636b36
Audit this contract →
← previous block·next block →recent activity