← previous blocknext block →recent activity
Analyzing
Block #106,932,444
21 transactions · 20 stateful · 2026-09-22 03:51:02 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,932,444 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w29w310w211w412w513w614w719w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab981df1…2941
0x34b655…2a6f
12 touches
15 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0x66774a98…88c8
0x34b655…2a6f
10 touches
10 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
10 touches
10 conflicts
0xec1dd684…b6b3
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xc01dd830…db33
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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 0xab981df1f6…082941
Audit this contract →
← previous block·next block →recent activity