← previous blocknext block →recent activity
Analyzing
Block #106,556,174
38 transactions · 35 stateful · 2026-09-20 20:16:13 UTC
Parallelism
47/100
Blocked
77%
Avg conflicts / tx
4.18
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #106,556,174 · 38 txs across 20 waves · depth 20
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
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w410w718w819w920w721w222w1023w1124w1127w1429w1532w18
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4beaf610…8a09
0x34b655…2a6f
16 touches
28 conflicts
0x1b25f260…c429
0x34b655…2a6f
16 touches
28 conflicts
0x735a86cd…b64d
0x34b655…2a6f
16 touches
28 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
16 touches
28 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
14 touches
21 conflicts
0xb2560305…f27d
0x34b655…2a6f
14 touches
21 conflicts
0x39561c15…c70f
0x34b655…2a6f
14 touches
21 conflicts
0x8590b692…b267
0x34b655…2a6f
12 touches
15 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
28 conflicts on slot 0x4beaf61066…448a09
Audit this contract →
← previous block·next block →recent activity