← previous blocknext block →recent activity
Analyzing
Block #106,372,403
20 transactions · 20 stateful · 2026-09-20 04:51:17 UTC
Parallelism
50/100
Blocked
65%
Avg conflicts / tx
2.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,372,403 · 20 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
1w02w13w24w35w48w09w310w312w413w514w515w616w717w818w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdd131fa…dbdb
0x34b655…2a6f
16 touches
28 conflicts
0x5f1ffb67…59a2
0x34b655…2a6f
12 touches
15 conflicts
0x0f270a31…640c
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0x6d43ee99…bdd5
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xfdd131fae1…f8dbdb
Audit this contract →
← previous block·next block →recent activity