← previous blocknext block →recent activity
Analyzing
Block #105,931,764
19 transactions · 19 stateful · 2026-09-18 15:53:28 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,931,764 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w08w210w011w312w113w414w415w516w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3a429191…9cda
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x34455398…05b9
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
4 touches
1 conflict
0x35c68080…aace
0x851145…3f07
4 touches
1 conflict
0x1afd1723…2a45
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x3a42919159…6b9cda
Audit this contract →
← previous block·next block →recent activity