← previous blocknext block →recent activity
Analyzing
Block #106,253,361
34 transactions · 33 stateful · 2026-09-19 18:52:14 UTC
Parallelism
53/100
Blocked
70%
Avg conflicts / tx
3.35
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #106,253,361 · 34 txs across 16 waves · depth 16
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
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w513w614w715w317w619w723w824w925w1026w1127w1228w1329w1430w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfccf4b5b…66ca
0x34b655…2a6f
26 touches
78 conflicts
0x949f6fc3…c2ae
0x34b655…2a6f
26 touches
78 conflicts
0x524f0872…0d12
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x9dd0a735…4d04
0x34b655…2a6f
10 touches
10 conflicts
0x5906754f…b584
0x34b655…2a6f
10 touches
10 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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 0xfccf4b5b29…a966ca
Audit this contract →
← previous block·next block →recent activity