← previous blocknext block →recent activity
Analyzing
Block #106,199,228
18 transactions · 17 stateful · 2026-09-19 14:19:42 UTC
Parallelism
61/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,199,228 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w412w513w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9dfeb9e0…e270
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x65e795ca…0320
0x34b655…2a6f
12 touches
15 conflicts
0x6a9e408e…3721
0x34b655…2a6f
12 touches
15 conflicts
0x68292fe7…d918
0x34b655…2a6f
10 touches
10 conflicts
0x839c0c71…bada
0x34b655…2a6f
10 touches
10 conflicts
0x890d2fe3…91d9
0x34b655…2a6f
10 touches
10 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x9dfeb9e01d…95e270
Audit this contract →
← previous block·next block →recent activity