← previous blocknext block →recent activity
Analyzing
Block #106,575,626
29 transactions · 27 stateful · 2026-09-20 21:54:07 UTC
Parallelism
72/100
Blocked
48%
Avg conflicts / tx
1.24
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,575,626 · 29 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
1w02w03w14w05w17w111w212w014w317w118w119w421w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4ee0b65a…6d40
0x34b655…2a6f
14 touches
21 conflicts
0xf820a074…e5b6
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7d6b9af1…9a38
0x34b655…2a6f
8 touches
6 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
8 touches
6 conflicts
0x8f63f383…6eda
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x502b3ee1…7f7c
0x34b655…2a6f
4 touches
1 conflict
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 0x4ee0b65a93…c56d40
Audit this contract →
← previous block·next block →recent activity