← previous blocknext block →recent activity
Analyzing
Block #84,177,034
13 transactions · 12 stateful · 2026-06-28 04:33:07 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,177,034 · 13 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
1w02w16w27w3
- 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
0x56c6a4d6…b69f
0x065c9d…c394
3 touches
1 conflict
0x09c5fda8…1776
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x0f28fb99…3d2f
0x1b6862…e19c
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x0bcaba7e…0e80
0x3bd359…433a
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