← previous blocknext block →recent activity
Analyzing
Block #106,568,093
21 transactions · 17 stateful · 2026-09-20 21:16:12 UTC
Parallelism
67/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,568,093 · 21 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
1w02w13w25w26w37w48w513w620w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xa57a72ed…64c2
0x34b655…2a6f
10 touches
10 conflicts
0x97394169…cfc0
0x34b655…2a6f
10 touches
10 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
10 touches
10 conflicts
0x556beb43…e627
0x34b655…2a6f
8 touches
6 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
8 touches
6 conflicts
0x69d2053b…935a
0x34b655…2a6f
8 touches
6 conflicts
0x7aa463de…e7b8
0x34b655…2a6f
8 touches
6 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
21 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity