← previous blocknext block →recent activity
Analyzing
Block #106,426,246
15 transactions · 14 stateful · 2026-09-20 09:22:15 UTC
Parallelism
73/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,426,246 · 15 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
1w02w13w14w26w07w111w112w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc321f86…4c7f
0x34b655…2a6f
6 touches
3 conflicts
0xf77fbd5a…8833
0x34b655…2a6f
4 touches
1 conflict
0xfdd131fa…dbdb
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2c2761c0…476e
0x34b655…2a6f
4 touches
1 conflict
0x3113c700…1e0e
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
0x34b655…2a6f
4 touches
1 conflict
0x49b9fdd5…9c16
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
3 conflicts on slot 0xfc321f869c…a24c7f
Audit this contract →
← previous block·next block →recent activity