← previous blocknext block →recent activity
Analyzing
Block #105,850,663
21 transactions · 20 stateful · 2026-09-18 09:04:24 UTC
Parallelism
52/100
Blocked
60%
Avg conflicts / tx
2.19
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,850,663 · 21 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w010w111w212w313w414w515w516w617w718w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x23529e13…6f25
0x34b655…2a6f
14 touches
21 conflicts
0x16bba458…258c
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x2827ae77…4368
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x4abfb389…18f4
0x34b655…2a6f
8 touches
6 conflicts
0x3da1337e…9c84
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
21 conflicts on slot 0x23529e136b…8a6f25
Audit this contract →
← previous block·next block →recent activity