← previous blocknext block →recent activity
Analyzing
Block #106,385,984
33 transactions · 32 stateful · 2026-09-20 05:59:39 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
1.27
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #106,385,984 · 33 txs across 12 waves · depth 12
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w08w410w111w513w615w716w817w818w919w1020w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd882484…aaa4
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xcd9ba26b…108d
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xf34802b3…9f0f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
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
21 conflicts on slot 0xdd882484c4…15aaa4
Audit this contract →
← previous block·next block →recent activity