← previous blocknext block →recent activity
Analyzing
Block #106,224,214
26 transactions · 24 stateful · 2026-09-19 16:25:30 UTC
Parallelism
65/100
Blocked
75%
Avg conflicts / tx
2.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,224,214 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w17w29w312w415w516w217w619w420w521w623w825w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xc737ce4f…a8d8
0x34b655…2a6f
14 touches
21 conflicts
0x690cb4c2…2ba3
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xacffc07d…b542
0xd32edf…ff58
9 touches
10 conflicts
0xd18a8dca…4530
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 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
28 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity