← previous blocknext block →recent activity
Analyzing
Block #106,956,665
71 transactions · 56 stateful · 2026-09-22 05:52:57 UTC
Parallelism
82/100
Blocked
63%
Avg conflicts / tx
2.37
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,956,665 · 71 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w28w214w117w221w324w437w644w445w151w152w253w954w1061w462w563w664w766w867w968w1069w1170w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6598470a…6ad7
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
20 touches
45 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
16 touches
28 conflicts
0x8d5fc820…1750
0x34b655…2a6f
16 touches
28 conflicts
0x0463db49…5d05
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x71ecf7c5…8b1e
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
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
55 conflicts on slot 0x6598470a71…b56ad7
Audit this contract →
← previous block·next block →recent activity