← previous blocknext block →recent activity
Analyzing
Block #106,551,576
34 transactions · 30 stateful · 2026-09-20 19:53:05 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,551,576 · 34 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
1w02w13w24w35w46w07w18w29w310w521w022w123w425w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a4b4833…cf01
0x34b655…2a6f
10 touches
10 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
10 touches
10 conflicts
0xbc8fb280…76a3
0x34b655…2a6f
10 touches
10 conflicts
0xd267927d…8eca
0xd32edf…ff58
9 touches
10 conflicts
0x1032f16c…a9b1
0x34b655…2a6f
8 touches
6 conflicts
0x21e79ad8…c5db
0x34b655…2a6f
8 touches
6 conflicts
0x2f50c84a…3640
0x34b655…2a6f
8 touches
6 conflicts
0x48828733…fd48
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 0x1a4b483324…02cf01
Audit this contract →
← previous block·next block →recent activity