← previous blocknext block →recent activity
Analyzing
Block #105,921,492
31 transactions · 27 stateful · 2026-09-18 15:01:45 UTC
Parallelism
65/100
Blocked
63%
Avg conflicts / tx
1.55
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,921,492 · 31 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w59w610w712w813w914w1016w417w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
16 touches
28 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xddd20e39…d524
0x34b655…2a6f
8 touches
6 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x83d8da70…20ab
0xd32edf…ff58
7 touches
6 conflicts
0x897f5aef…a6d1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c0
0x1b6862…e19c
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: 0xf5b5f7f8…a36d70
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity