← previous blocknext block →recent activity
Analyzing
Block #105,851,974
28 transactions · 26 stateful · 2026-09-18 09:11:00 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1.64
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,851,974 · 28 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w010w111w213w116w317w418w519w620w721w824w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x382434ca…96b5
0x34b655…2a6f
16 touches
28 conflicts
0x38d6111f…33a0
0x34b655…2a6f
14 touches
21 conflicts
0xec2a8d79…70cb
0x34b655…2a6f
10 touches
10 conflicts
0xee8237bd…46ad
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4681609f…6493
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
28 conflicts on slot 0x382434ca57…4d96b5
Audit this contract →
← previous block·next block →recent activity