← previous blocknext block →recent activity
Analyzing
Block #105,402,272
49 transactions · 41 stateful · 2026-09-16 19:26:12 UTC
Parallelism
73/100
Blocked
71%
Avg conflicts / tx
2.53
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,402,272 · 49 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w19w211w313w421w322w423w524w625w726w827w930w1041w242w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xf42e9f99…5f09
0x34b655…2a6f
12 touches
15 conflicts
0x7bb6e120…2a0f
0x34b655…2a6f
12 touches
15 conflicts
0x100812e9…12b7
0x34b655…2a6f
12 touches
15 conflicts
0x9d6a99f9…da64
0x34b655…2a6f
10 touches
10 conflicts
0xaaae2ec0…60a6
0x34b655…2a6f
10 touches
10 conflicts
0xab3ad3dc…2a56
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity