← previous blocknext block →recent activity
Analyzing
Block #102,374,569
39 transactions · 38 stateful · 2026-09-06 04:30:06 UTC
Parallelism
85/100
Blocked
32%
Avg conflicts / tx
0.49
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,374,569 · 39 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
1w02w13w28w39w411w317w218w319w434w435w537w438w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb682e7d…dde9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xfa324e43…8896
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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
6 conflicts on slot 0xfb682e7d8c…dcdde9
Audit this contract →
← previous block·next block →recent activity