← previous blocknext block →recent activity
Analyzing
Block #83,876,048
13 transactions · 11 stateful · 2026-06-26 19:08:07 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #83,876,048 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1a4be6ea…5aa6
0x0a4fcb…a602
2 touches
0 conflicts
0x1a4be6ea…5aa7
0x0a4fcb…a602
2 touches
0 conflicts
0x1a4be6ea…5aa8
0x0a4fcb…a602
2 touches
0 conflicts
0x8d8df084…c9b3
0x0a4fcb…a602
2 touches
0 conflicts
0x6bd9b2de…7d72
0x0f2610…0edc
2 touches
0 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
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