← previous blocknext block →recent activity
Analyzing
Block #106,014,486
17 transactions · 17 stateful · 2026-09-18 22:49:58 UTC
Parallelism
65/100
Blocked
59%
Avg conflicts / tx
1.47
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,014,486 · 17 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
1w02w13w24w05w16w28w310w411w512w513w315w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x735a86cd…b64d
0x34b655…2a6f
10 touches
10 conflicts
0x3dbf1b9b…c0df
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x4979282b…2934
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x482471ad…122f
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
10 conflicts on slot 0x735a86cd19…53b64d
Audit this contract →
← previous block·next block →recent activity