← previous blocknext block →recent activity
Analyzing
Block #105,848,963
29 transactions · 27 stateful · 2026-09-18 08:55:51 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
1.83
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #105,848,963 · 29 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
1w02w13w24w25w313w416w518w719w821w1023w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x97e4c862…4419
0x34b655…2a6f
18 touches
36 conflicts
0xaebb20da…2933
0x34b655…2a6f
16 touches
28 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x4118bd12…924a
0x34b655…2a6f
8 touches
6 conflicts
0xc09c3422…3c8b
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xfac61869…a562
0x1b6862…e19c
6 touches
3 conflicts
0x161d8cf7…654b
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
36 conflicts on slot 0x97e4c86258…af4419
Audit this contract →
← previous block·next block →recent activity