← previous blocknext block →recent activity
Analyzing
Block #106,388,670
17 transactions · 17 stateful · 2026-09-20 06:13:09 UTC
Parallelism
47/100
Blocked
53%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,388,670 · 17 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w28w29w310w411w512w613w714w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89eaf36a…4e48
0x34b655…2a6f
14 touches
21 conflicts
0x2686eb58…7c02
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x038b9243…553d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5060cdde…445d
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x65067517…93f7
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 0x89eaf36ae4…6e4e48
Audit this contract →
← previous block·next block →recent activity