← previous blocknext block →recent activity
Analyzing
Block #106,235,202
35 transactions · 35 stateful · 2026-09-19 17:20:51 UTC
Parallelism
57/100
Blocked
71%
Avg conflicts / tx
3.11
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #106,235,202 · 35 txs across 15 waves · depth 15
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
wave w12
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w512w613w714w830w1031w1132w1233w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
22 touches
55 conflicts
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0xcfe180d7…b5a4
0x34b655…2a6f
16 touches
28 conflicts
0x73b87bc2…457a
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc08af837…3db6
0x34b655…2a6f
12 touches
15 conflicts
0xc102b2b7…57a2
0x34b655…2a6f
12 touches
15 conflicts
0xc5f336ca…912e
0x34b655…2a6f
12 touches
15 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
55 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity