← previous blocknext block →recent activity
Analyzing
Block #105,574,881
22 transactions · 20 stateful · 2026-09-17 09:54:53 UTC
Parallelism
73/100
Blocked
55%
Avg conflicts / tx
0.95
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #105,574,881 · 22 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
1w04w05w16w210w111w212w113w214w315w216w417w521w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x18a3102e…8959
0x34b655…2a6f
8 touches
6 conflicts
0xf48fa71e…bb52
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xeaf0ccf5…3957
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
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
6 conflicts on slot 0x18a3102e41…8d8959
Audit this contract →
← previous block·next block →recent activity