← previous blocknext block →recent activity
Analyzing
Block #106,420,322
24 transactions · 23 stateful · 2026-09-20 08:52:27 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,420,322 · 24 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
1w02w13w14w25w06w114w215w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9aa25d9…3345
0x34b655…2a6f
8 touches
6 conflicts
0xa1062458…ab6d
0x34b655…2a6f
8 touches
6 conflicts
0x524f0872…0d12
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x1b25f260…c429
0x34b655…2a6f
6 touches
3 conflicts
0xfb1d5846…56af
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xe9aa25d94d…3b3345
Audit this contract →
← previous block·next block →recent activity