← previous blocknext block →recent activity
Analyzing
Block #106,464,347
21 transactions · 19 stateful · 2026-09-20 12:34:04 UTC
Parallelism
67/100
Blocked
68%
Avg conflicts / tx
1.76
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,464,347 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w17w28w29w310w411w512w514w618w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xd563f3a1…94b1
0x34b655…2a6f
10 touches
10 conflicts
0x228da3f5…c2bf
0x34b655…2a6f
8 touches
6 conflicts
0x54563e2b…7469
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x02fa927d…6468
0x34b655…2a6f
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity