← previous blocknext block →recent activity
Analyzing
Block #106,921,928
21 transactions · 20 stateful · 2026-09-22 02:58:06 UTC
Parallelism
71/100
Blocked
70%
Avg conflicts / tx
1.48
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,921,928 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w18w29w010w011w112w213w314w415w116w417w520w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
12 touches
15 conflicts
0xa725b52a…4a88
0x34b655…2a6f
10 touches
10 conflicts
0xe720a4c6…8eb0
0x34b655…2a6f
10 touches
10 conflicts
0xef7ba85a…7772
0xd32edf…ff58
9 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 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
15 conflicts on slot 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity