← previous blocknext block →recent activity
Analyzing
Block #106,934,440
36 transactions · 32 stateful · 2026-09-22 04:01:05 UTC
Parallelism
81/100
Blocked
47%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,934,440 · 36 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w09w011w113w216w217w222w424w225w330w531w635w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0edadb9…dbfe
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xab981df1…2941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0x0747620e…9783
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0xa0edadb925…12dbfe
Audit this contract →
← previous block·next block →recent activity