← previous blocknext block →recent activity
Analyzing
Block #106,924,188
20 transactions · 19 stateful · 2026-09-22 03:09:29 UTC
Parallelism
70/100
Blocked
37%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,924,188 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w19w215w316w417w518w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x59285bbf…c491
0x34b655…2a6f
12 touches
15 conflicts
0x34c48330…703f
0x34b655…2a6f
12 touches
15 conflicts
0xea79e6d3…68ad
0x34b655…2a6f
10 touches
10 conflicts
0xdf64e5e6…75e8
0x34b655…2a6f
6 touches
3 conflicts
0x72055767…d5a5
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0xec63e4f6…4778
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
15 conflicts on slot 0x59285bbfe1…d1c491
Audit this contract →
← previous block·next block →recent activity