← previous blocknext block →recent activity
Analyzing
Block #103,049,832
30 transactions · 27 stateful · 2026-09-08 13:20:54 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #103,049,832 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w113w317w418w220w221w523w629w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac389ba9…8b45
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x3ff1d113…b6d4
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0xd59f6ed1…03eb
0x1b6862…e19c
8 touches
6 conflicts
0x0978e047…3655
0xd32edf…ff58
7 touches
6 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 0xac389ba9d1…e18b45
Audit this contract →
← previous block·next block →recent activity