← previous blocknext block →recent activity
Analyzing
Block #106,952,006
21 transactions · 21 stateful · 2026-09-22 05:29:30 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,952,006 · 21 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
1w03w04w15w26w37w09w113w014w015w116w217w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5fad6fee…7714
0x34b655…2a6f
6 touches
3 conflicts
0xeb179a44…5477
0x34b655…2a6f
6 touches
3 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
4 touches
1 conflict
0x76e62299…b2dc
0x34b655…2a6f
4 touches
1 conflict
0x7871a8f4…2527
0x34b655…2a6f
4 touches
1 conflict
0xe07205ad…1ccd
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 0x49b9fdd5ff…6f9c16
Audit this contract →
← previous block·next block →recent activity