← previous blocknext block →recent activity
Analyzing
Block #101,967,246
17 transactions · 16 stateful · 2026-09-04 18:05:50 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,967,246 · 17 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
1w02w13w24w05w19w310w012w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0000
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0003
0x116e7d…d8f1
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c1
0x1b6862…e19c
6 touches
3 conflicts
0x692a4122…76b8
0x350035…7777
6 touches
3 conflicts
0xb7143610…adc4
0x3bd359…433a
6 touches
3 conflicts
0xc97c2709…2f4a
0xd32edf…ff58
5 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: 0x116e7d07…d7d8f1
3 conflicts on slot 0x0000000000…000000
Audit this contract →
← previous block·next block →recent activity