← previous blocknext block →recent activity
Analyzing
Block #80,825,999
30 transactions · 18 stateful · 2026-06-12 15:56:18 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,825,999 · 30 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
1w02w14w06w113w014w215w316w422w324w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x565818b0…80a3
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
4 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x1cbcefba…d051
0x34b655…2a6f
4 touches
1 conflict
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x42bb0ac5…6b33
0x34b655…2a6f
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 0x565818b083…1680a3
Audit this contract →
← previous block·next block →recent activity