← previous blocknext block →recent activity
Analyzing
Block #105,749,226
24 transactions · 23 stateful · 2026-09-18 00:32:27 UTC
Parallelism
54/100
Blocked
57%
Avg conflicts / tx
2.25
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,749,226 · 24 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w27w311w312w414w515w616w717w818w919w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x213b816c…a5e0
0x34b655…2a6f
12 touches
15 conflicts
0xdb1e37cb…90c9
0x34b655…2a6f
10 touches
10 conflicts
0xe35a20aa…b94b
0x34b655…2a6f
10 touches
10 conflicts
0x790debba…6bf8
0x34b655…2a6f
8 touches
6 conflicts
0x27034002…2f27
0x34b655…2a6f
8 touches
6 conflicts
0xeaf62fe6…0634
0x34b655…2a6f
6 touches
3 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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity