← previous blocknext block →recent activity
Analyzing
Block #83,875,814
10 transactions · 9 stateful · 2026-06-26 19:06:34 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,875,814 · 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
1w02w03w14w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x0836218c…2d68
0x34b655…2a6f
2 touches
0 conflicts
0x13528a92…ac8b
0x34b655…2a6f
2 touches
0 conflicts
0x1b8b89d6…e2f6
0x34b655…2a6f
2 touches
0 conflicts
0x2d53de17…1a11
0x34b655…2a6f
2 touches
0 conflicts
0x4ca600fb…0928
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity