← previous blocknext block →recent activity
Analyzing
Block #84,132,928
20 transactions · 15 stateful · 2026-06-27 23:39:45 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,132,928 · 20 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
6w010w112w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b7af531…48f1
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe003c4c1…62b8
0xd32edf…ff58
3 touches
1 conflict
0xad436b12…f632
0x1111b3…4111
2 touches
0 conflicts
0xb3eae1cb…7249
0x1111b3…4111
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
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-WETH/USDC
3 conflicts on slot 0x7b7af53137…5748f1
Audit this contract →
← previous block·next block →recent activity