← previous blocknext block →recent activity
Analyzing
Block #106,337,143
26 transactions · 25 stateful · 2026-09-20 01:53:50 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
1.38
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,337,143 · 26 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
1w02w14w05w07w010w111w214w216w218w322w323w424w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0xb90556e3…0e6a
0x34b655…2a6f
12 touches
15 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x59907802…234c
0xd32edf…ff58
7 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 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity