← previous blocknext block →recent activity
Analyzing
Block #106,944,794
22 transactions · 21 stateful · 2026-09-22 04:53:12 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,944,794 · 22 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
1w02w13w24w35w49w410w519w020w121w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a286811…499f
0x34b655…2a6f
8 touches
6 conflicts
0x858e40c0…7e30
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xf8480e2a…dff3
0x1b6862…e19c
6 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
6 conflicts on slot 0x2a28681175…0a499f
Audit this contract →
← previous block·next block →recent activity