← previous blocknext block →recent activity
Analyzing
Block #83,209,282
12 transactions · 6 stateful · 2026-06-23 16:57:16 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,209,282 · 12 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9e20cccf…19cc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
2 touches
0 conflicts
0x1484b3a0…e3bf
0x34b655…2a6f
2 touches
0 conflicts
0x184b47c9…59df
0x34b655…2a6f
2 touches
0 conflicts
0x19b389b8…0cad
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
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 0x9e20cccfee…8c19cc
Audit this contract →
← previous block·next block →recent activity