← previous blocknext block →recent activity
Analyzing
Block #106,185,251
28 transactions · 26 stateful · 2026-09-19 13:09:21 UTC
Parallelism
64/100
Blocked
69%
Avg conflicts / tx
2.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,185,251 · 28 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
1w02w13w24w35w06w17w29w310w312w413w514w615w716w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xd41f5136…97c6
0x34b655…2a6f
16 touches
28 conflicts
0x3cd30284…22d8
0x34b655…2a6f
14 touches
21 conflicts
0x56409df0…27cd
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0xd0ec60a1…d246
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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