← previous blocknext block →recent activity
Analyzing
Block #106,224,802
20 transactions · 19 stateful · 2026-09-19 16:28:27 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.9
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,224,802 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w014w018w119w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638cd0f2…cb93
0x34b655…2a6f
12 touches
15 conflicts
0x31d0d65b…126b
0x34b655…2a6f
12 touches
15 conflicts
0xf788c790…e66f
0x34b655…2a6f
8 touches
6 conflicts
0x469dac8d…3411
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xc30ccd20…698a
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x096b3a05…3eb4
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
15 conflicts on slot 0x638cd0f243…88cb93
Audit this contract →
← previous block·next block →recent activity