← previous blocknext block →recent activity
Analyzing
Block #106,551,627
28 transactions · 26 stateful · 2026-09-20 19:53:20 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
1.46
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,551,627 · 28 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
1w02w13w24w35w46w59w526w527w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x5d0915af…762d
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x5f72d58f…c445
0x34b655…2a6f
10 touches
10 conflicts
0xb8dc136f…fb16
0xc8689a…ee79
10 touches
10 conflicts
0xaf59c69d…c904
0x37db7f…ec7b
10 touches
10 conflicts
0xcf94604f…25e6
0x34b655…2a6f
10 touches
10 conflicts
0x8765edd1…a7d5
0x34b655…2a6f
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity