← previous blocknext block →recent activity
Analyzing
Block #106,403,584
22 transactions · 21 stateful · 2026-09-20 07:28:12 UTC
Parallelism
82/100
Blocked
48%
Avg conflicts / tx
0.86
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,403,584 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w17w08w111w113w215w216w118w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8b52b75c…8a0d
0xa6afd3…d132
6 touches
3 conflicts
0x02fa927d…6468
0x34b655…2a6f
6 touches
3 conflicts
0x4265984a…a7d2
0x34b655…2a6f
6 touches
3 conflicts
0x9d796412…aacc
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x71f4e95f…8e98
0xa6afd3…d132
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity