← previous blocknext block →recent activity
Analyzing
Block #106,184,567
35 transactions · 33 stateful · 2026-09-19 13:05:55 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,184,567 · 35 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
1w02w13w24w35w49w010w111w112w219w329w230w531w332w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x0fc536fb…1aa1
0x34b655…2a6f
10 touches
10 conflicts
0x1033430e…7991
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x10c19272…7445
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity