← previous blocknext block →recent activity
Analyzing
Block #84,058,713
17 transactions · 10 stateful · 2026-06-27 15:25:22 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,058,713 · 17 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
12w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x763dd151…d9de
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
2 touches
0 conflicts
0x2d95c7ff…1596
0x34b655…2a6f
2 touches
0 conflicts
0x371dc39b…f5a9
0x34b655…2a6f
2 touches
0 conflicts
0x3a8ec2fb…38c3
0x34b655…2a6f
2 touches
0 conflicts
0x4042e6b4…b2ff
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
1 conflict on slot 0x763dd151da…97d9de
Audit this contract →
← previous block·next block →recent activity