← previous blocknext block →recent activity
Analyzing
Block #105,849,826
64 transactions · 50 stateful · 2026-09-18 09:00:11 UTC
Parallelism
72/100
Blocked
70%
Avg conflicts / tx
2.3
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #105,849,826 · 64 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
1w03w04w06w17w29w213w116w219w221w435w338w140w541w642w143w645w848w1149w1251w1455w256w360w763w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
20 touches
45 conflicts
0x8063b7e8…32fd
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
12 touches
15 conflicts
0x2827ae77…4368
0x34b655…2a6f
12 touches
15 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
10 touches
10 conflicts
0x9dccd2a9…2790
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
45 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity