← previous blocknext block →recent activity
Analyzing
Block #106,386,323
23 transactions · 22 stateful · 2026-09-20 06:01:21 UTC
Parallelism
57/100
Blocked
55%
Avg conflicts / tx
2.3
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,386,323 · 23 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
1w02w03w14w25w07w310w412w313w514w618w619w720w821w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4b3d9f0a…5036
0x34b655…2a6f
16 touches
28 conflicts
0x174723f5…8bc0
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x0ed7cc0b…ee52
0x34b655…2a6f
8 touches
6 conflicts
0xd6d040d9…9ae3
0x34b655…2a6f
6 touches
3 conflicts
0x74e46435…fdcd
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
28 conflicts on slot 0x4b3d9f0ae1…0e5036
Audit this contract →
← previous block·next block →recent activity