← previous blocknext block →recent activity
Analyzing
Block #84,490,722
20 transactions · 18 stateful · 2026-06-29 15:23:45 UTC
Parallelism
75/100
Blocked
56%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,490,722 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w110w112w213w314w215w418w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3287e4ec…eaa3
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x975680c7…0e39
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xff4ee2c4…6e5e
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
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 0x3287e4ecfd…5aeaa3
Audit this contract →
← previous block·next block →recent activity