← previous blocknext block →recent activity
Analyzing
Block #106,198,313
34 transactions · 31 stateful · 2026-09-19 14:15:05 UTC
Parallelism
79/100
Blocked
48%
Avg conflicts / tx
1.26
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,198,313 · 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
1w02w13w24w35w46w28w010w011w112w014w120w122w225w528w329w330w431w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xd8cadc0d…776e
0x34b655…2a6f
10 touches
10 conflicts
0x0fcabe0b…a614
0x34b655…2a6f
10 touches
10 conflicts
0xb4d5a6d4…eddf
0xd32edf…ff58
9 touches
10 conflicts
0x1fdb3ffb…6422
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
8 touches
6 conflicts
0xd597209e…9800
0x34b655…2a6f
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity