← previous blocknext block →recent activity
Analyzing
Block #103,210,388
18 transactions · 17 stateful · 2026-09-09 02:50:27 UTC
Parallelism
44/100
Blocked
59%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #103,210,388 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w49w512w615w717w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb75367ff…a2b7
0x34b655…2a6f
14 touches
21 conflicts
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 conflicts
0xcb10192b…9066
0x34b655…2a6f
10 touches
10 conflicts
0x045532dd…4b7d
0x34b655…2a6f
10 touches
10 conflicts
0xb40e601f…bf98
0x34b655…2a6f
8 touches
6 conflicts
0x7dbacbb4…9957
0x34b655…2a6f
6 touches
3 conflicts
0x8525d5a7…df09
0x34b655…2a6f
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 0xb75367ffdb…6fa2b7
Audit this contract →
← previous block·next block →recent activity