← previous blocknext block →recent activity
Analyzing
Block #83,853,870
20 transactions · 19 stateful · 2026-06-26 16:40:10 UTC
Parallelism
70/100
Blocked
47%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,853,870 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w37w08w19w213w214w415w316w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfc5f346…7b42
0x40c49f…2af0
8 touches
6 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x784d7a94…94a2
0x1b6862…e19c
6 touches
3 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: 0x40c49f17…d22af0
6 conflicts on slot 0xdfc5f34630…0b7b42
Audit this contract →
← previous block·next block →recent activity