← previous blocknext block →recent activity
Analyzing
Block #106,916,070
18 transactions · 18 stateful · 2026-09-22 02:28:37 UTC
Parallelism
67/100
Blocked
72%
Avg conflicts / tx
2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,916,070 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w58w09w110w211w112w213w314w415w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb5c7c6aa…fdba
0x34b655…2a6f
12 touches
15 conflicts
0x7b7522e7…2c46
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x158cd73a…d47b
0x34b655…2a6f
10 touches
10 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 0xb5c7c6aad4…acfdba
Audit this contract →
← previous block·next block →recent activity