← previous blocknext block →recent activity
Analyzing
Block #102,875,498
26 transactions · 25 stateful · 2026-09-07 22:43:01 UTC
Parallelism
69/100
Blocked
48%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,875,498 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w27w08w313w414w516w617w018w119w020w123w324w425w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5ad540d…72da
0x34b655…2a6f
8 touches
6 conflicts
0x2202504e…fad0
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x4d42f16e…a6ca
0x1b6862…e19c
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
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 0xe5ad540d31…3b72da
Audit this contract →
← previous block·next block →recent activity