← previous blocknext block →recent activity
Analyzing
Block #102,210,039
25 transactions · 20 stateful · 2026-09-05 14:36:35 UTC
Parallelism
56/100
Blocked
55%
Avg conflicts / tx
1.2
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #102,210,039 · 25 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w09w310w416w517w618w719w821w123w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcba8cd9…77c0
0x34b655…2a6f
14 touches
21 conflicts
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6aa624fd…a852
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
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
21 conflicts on slot 0xfcba8cd918…5e77c0
Audit this contract →
← previous block·next block →recent activity