← previous blocknext block →recent activity
Analyzing
Block #106,377,551
30 transactions · 29 stateful · 2026-09-20 05:17:12 UTC
Parallelism
70/100
Blocked
72%
Avg conflicts / tx
2.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,377,551 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w110w211w412w415w218w320w321w422w523w625w427w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x72a1afae…0b1c
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
10 touches
10 conflicts
0xc6a8c250…737b
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
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
21 conflicts on slot 0x72a1afae64…930b1c
Audit this contract →
← previous block·next block →recent activity