← previous blocknext block →recent activity
Analyzing
Block #106,099,965
22 transactions · 20 stateful · 2026-09-19 06:00:08 UTC
Parallelism
68/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,099,965 · 22 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
1w02w13w14w25w38w010w211w112w316w417w518w621w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1528762d…c303
0x34b655…2a6f
12 touches
15 conflicts
0x35bf9d78…28bd
0x34b655…2a6f
10 touches
10 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x9ba10aad…9bc5
0x34b655…2a6f
8 touches
6 conflicts
0xe7702ef2…3e4b
0x34b655…2a6f
6 touches
3 conflicts
0x2130a548…c1de
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
15 conflicts on slot 0x1528762d71…bec303
Audit this contract →
← previous block·next block →recent activity