← previous blocknext block →recent activity
Analyzing
Block #106,186,246
26 transactions · 24 stateful · 2026-09-19 13:14:22 UTC
Parallelism
77/100
Blocked
38%
Avg conflicts / tx
0.96
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,186,246 · 26 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
3w04w15w26w37w017w019w220w421w422w524w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbf974a4…b232
0x34b655…2a6f
10 touches
10 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
10 touches
10 conflicts
0xfefb0189…f726
0x34b655…2a6f
10 touches
10 conflicts
0x9fda36ae…2055
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x9a6d78b0…b736
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0xc0f4fb1c…a3d1
0x34b655…2a6f
6 touches
3 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 0xdbf974a4cf…a9b232
Audit this contract →
← previous block·next block →recent activity