← previous blocknext block →recent activity
Analyzing
Block #106,382,440
38 transactions · 36 stateful · 2026-09-20 05:41:48 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.76
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,382,440 · 38 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w419w420w526w636w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd9ba26b…108d
0x34b655…2a6f
14 touches
21 conflicts
0x89eaf36a…4e48
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x8d175439…fb79
0x34b655…2a6f
8 touches
6 conflicts
0x2686eb58…7c02
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2836d18c…d85c
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xcd9ba26bf8…62108d
Audit this contract →
← previous block·next block →recent activity