← previous blocknext block →recent activity
Analyzing
Block #102,867,386
19 transactions · 19 stateful · 2026-09-07 22:02:12 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,867,386 · 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
1w02w13w24w25w06w17w39w210w311w312w413w414w515w317w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x46e2bb67…d8b3
0x34b655…2a6f
10 touches
10 conflicts
0x359866c7…de7b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x6fd9ae7c…e981
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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 0x46e2bb6759…04d8b3
Audit this contract →
← previous block·next block →recent activity