← previous blocknext block →recent activity
Analyzing
Block #106,224,328
46 transactions · 45 stateful · 2026-09-19 16:26:04 UTC
Parallelism
61/100
Blocked
73%
Avg conflicts / tx
4.11
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #106,224,328 · 46 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w29w310w411w512w119w620w723w826w833w1336w1642w244w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x638cd0f2…cb93
0x34b655…2a6f
30 touches
105 conflicts
0x1b25f260…c429
0x34b655…2a6f
20 touches
45 conflicts
0xe22ab637…7a8e
0x34b655…2a6f
14 touches
21 conflicts
0xa6464996…3af9
0x34b655…2a6f
14 touches
21 conflicts
0xfab2647b…38f2
0x34b655…2a6f
12 touches
15 conflicts
0x3f6d0224…a5cf
0x34b655…2a6f
12 touches
15 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
12 touches
15 conflicts
0x525bf8cd…bd48
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
105 conflicts on slot 0x638cd0f243…88cb93
Audit this contract →
← previous block·next block →recent activity