← previous blocknext block →recent activity
Analyzing
Block #106,282,936
65 transactions · 50 stateful · 2026-09-19 21:21:04 UTC
Parallelism
80/100
Blocked
64%
Avg conflicts / tx
1.69
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #106,282,936 · 65 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
7w010w111w012w013w114w215w116w018w120w021w125w328w229w330w231w240w441w249w757w363w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x4ee0b65a…6d40
0x34b655…2a6f
16 touches
28 conflicts
0x1774fb3b…e6c1
0xd32edf…ff58
15 touches
28 conflicts
0x10c769eb…0c30
0x34b655…2a6f
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5e2ea201…12de
0x34b655…2a6f
8 touches
6 conflicts
0xacae3599…e8c9
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
45 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity