← previous blocknext block →recent activity
Analyzing
Block #105,470,244
25 transactions · 22 stateful · 2026-09-17 01:08:17 UTC
Parallelism
84/100
Blocked
41%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,470,244 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w07w18w09w115w217w218w322w024w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5631dbd8…2cc5
0x34b655…2a6f
8 touches
6 conflicts
0x7d0eaae2…60b7
0x34b655…2a6f
8 touches
6 conflicts
0xaaf36ccb…f35c
0x34b655…2a6f
6 touches
3 conflicts
0x173b64af…6c43
0x34b655…2a6f
6 touches
3 conflicts
0xda50c9d5…674e
0x34b655…2a6f
6 touches
3 conflicts
0xf139b130…d132
0x34b655…2a6f
6 touches
3 conflicts
0x67dd4a7b…e352
0x34b655…2a6f
6 touches
3 conflicts
0x18978822…2623
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 0x5631dbd85d…e72cc5
Audit this contract →
← previous block·next block →recent activity