← previous blocknext block →recent activity
Analyzing
Block #81,878,314
25 transactions · 18 stateful · 2026-06-17 12:46:50 UTC
Parallelism
92/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,878,314 · 25 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
2w03w04w110w011w114w015w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x112cf8ad…6e4f
0xa6afd3…d132
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x3181bd2d…cf15
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xaa7ee7…f0e4
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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 0x112cf8adc5…856e4f
Audit this contract →
← previous block·next block →recent activity