← previous blocknext block →recent activity
Analyzing
Block #106,952,383
24 transactions · 23 stateful · 2026-09-22 05:31:24 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,952,383 · 24 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
1w04w05w16w27w08w111w012w113w214w215w117w218w119w320w221w322w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdf64e5e6…75e8
0x34b655…2a6f
8 touches
6 conflicts
0x085d5985…c9cd
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x56dd2175…c71f
0x34b655…2a6f
6 touches
3 conflicts
0x6252e2ae…f33f
0xa6afd3…d132
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
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
6 conflicts on slot 0xdf64e5e6b0…c975e8
Audit this contract →
← previous block·next block →recent activity