← previous blocknext block →recent activity
Analyzing
Block #102,478,939
19 transactions · 18 stateful · 2026-09-06 13:18:55 UTC
Parallelism
68/100
Blocked
61%
Avg conflicts / tx
1.37
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,478,939 · 19 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
1w02w13w25w36w07w18w09w112w213w315w416w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d2d23d3…8a3a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x18447597…123b
0x34b655…2a6f
8 touches
6 conflicts
0x290ffc4e…5f2b
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x78694995…f66b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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: Perpl
10 conflicts on slot 0x0d2d23d3eb…148a3a
Audit this contract →
← previous block·next block →recent activity