← previous blocknext block →recent activity
Analyzing
Block #106,215,292
20 transactions · 17 stateful · 2026-09-19 15:40:35 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,215,292 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w211w212w313w014w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55d48e94…6f58
0x34b655…2a6f
8 touches
6 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
8 touches
6 conflicts
0xe098738f…9bbe
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x12503a94…ffdb
0x34b655…2a6f
4 touches
1 conflict
0x22891c92…012d
0x34b655…2a6f
4 touches
1 conflict
0x3503cea1…51ba
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
6 conflicts on slot 0x55d48e9457…366f58
Audit this contract →
← previous block·next block →recent activity