← previous blocknext block →recent activity
Analyzing
Block #84,190,710
10 transactions · 10 stateful · 2026-06-28 06:04:09 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,190,710 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc05b880b…7746
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x02daf029…2e29
0x34b655…2a6f
2 touches
0 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
2 touches
0 conflicts
0x176258bc…0301
0x34b655…2a6f
2 touches
0 conflicts
0x1e346a85…e9c5
0x34b655…2a6f
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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
1 conflict on slot 0xc05b880b59…957746
Audit this contract →
← previous block·next block →recent activity