← previous blocknext block →recent activity
Analyzing
Block #105,848,641
16 transactions · 15 stateful · 2026-09-18 08:54:14 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,848,641 · 16 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
1w02w13w24w05w110w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c5120ac…af7a
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x339e57df…686b
0x34b655…2a6f
10 touches
10 conflicts
0x29cd05f5…390c
0x34b655…2a6f
10 touches
10 conflicts
0x7b67f6cf…0aab
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0x37699b20…1076
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
15 conflicts on slot 0x2c5120ac14…9daf7a
Audit this contract →
← previous block·next block →recent activity