← previous blocknext block →recent activity
Analyzing
Block #105,850,344
31 transactions · 29 stateful · 2026-09-18 09:02:48 UTC
Parallelism
45/100
Blocked
69%
Avg conflicts / tx
3.94
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,850,344 · 31 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w211w112w213w314w415w516w617w718w819w920w1021w1122w1223w1328w1429w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc9915b5…542c
0x34b655…2a6f
28 touches
91 conflicts
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x3eb33a35…5bb4
0x34b655…2a6f
10 touches
10 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0xcd5c0ecb…4b5f
0x34b655…2a6f
10 touches
10 conflicts
0x59a133dd…7982
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
91 conflicts on slot 0xdc9915b513…2b542c
Audit this contract →
← previous block·next block →recent activity