← previous blocknext block →recent activity
Analyzing
Block #105,852,327
37 transactions · 35 stateful · 2026-09-18 09:12:46 UTC
Parallelism
60/100
Blocked
63%
Avg conflicts / tx
2.95
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,852,327 · 37 txs across 15 waves · depth 15
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
wave w13
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w010w011w114w116w217w318w419w520w621w722w823w924w1025w1126w1227w1334w235w336w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x831f75b4…945d
0x34b655…2a6f
24 touches
66 conflicts
0x03e3cc82…13dc
0x34b655…2a6f
16 touches
28 conflicts
0x0281e083…66b4
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
14 touches
21 conflicts
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xf788c790…e66f
0x34b655…2a6f
10 touches
10 conflicts
0x4d4389b2…6e07
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
66 conflicts on slot 0x831f75b4aa…17945d
Audit this contract →
← previous block·next block →recent activity