← previous blocknext block →recent activity
Analyzing
Block #106,944,695
24 transactions · 23 stateful · 2026-09-22 04:52:42 UTC
Parallelism
71/100
Blocked
61%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,944,695 · 24 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
1w02w13w24w35w47w18w010w211w313w414w516w119w620w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x12f082fb…ce6b
0x34b655…2a6f
10 touches
10 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
8 touches
6 conflicts
0x95523e2a…4c01
0x065c9d…c394
8 touches
6 conflicts
0x17ac986c…cedb
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xe924603d…52c3
0xd32edf…ff58
5 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
10 conflicts on slot 0x12f082fb0e…6ece6b
Audit this contract →
← previous block·next block →recent activity