← previous blocknext block →recent activity
Analyzing
Block #106,924,379
26 transactions · 24 stateful · 2026-09-22 03:10:27 UTC
Parallelism
69/100
Blocked
63%
Avg conflicts / tx
1.69
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,924,379 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w210w311w412w513w614w718w421w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
16 touches
28 conflicts
0xd8797a00…4c4d
0x34b655…2a6f
16 touches
28 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
16 touches
28 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
0x794b8f81…3eac
0x1b6862…e19c
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
28 conflicts on slot 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity