← previous blocknext block →recent activity
Analyzing
Block #84,358,872
14 transactions · 12 stateful · 2026-06-29 00:44:48 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,358,872 · 14 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
1w02w03w15w08w19w110w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x975680c7…0e39
0xa6afd3…d132
6 touches
3 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3287e4ec…eaa3
0xa6afd3…d132
4 touches
1 conflict
0x5a5dd7b4…fba4
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x7c93b38a…9e69
0x34b655…2a6f
2 touches
0 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
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 0x975680c7cb…460e39
Audit this contract →
← previous block·next block →recent activity