← previous blocknext block →recent activity
Analyzing
Block #106,541,054
21 transactions · 21 stateful · 2026-09-20 19:00:08 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
0.95
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,541,054 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w07w29w313w416w017w418w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x524f0872…0d12
0x34b655…2a6f
4 touches
1 conflict
0x543f4651…59d0
0x34b655…2a6f
4 touches
1 conflict
0x5c3ecb74…af1d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity