← previous blocknext block →recent activity
Analyzing
Block #84,194,617
25 transactions · 23 stateful · 2026-06-28 06:30:09 UTC
Parallelism
80/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,194,617 · 25 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
1w02w15w06w07w08w19w110w011w012w213w314w415w417w118w019w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3287e4ec…eaa3
0xa6afd3…d132
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x975680c7…0e39
0xa6afd3…d132
4 touches
1 conflict
0x75cdffd8…c217
0x34b655…2a6f
4 touches
1 conflict
0xda7f9bd2…e332
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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
6 conflicts on slot 0x3287e4ecfd…5aeaa3
Audit this contract →
← previous block·next block →recent activity