← previous blocknext block →recent activity
Analyzing
Block #106,952,071
35 transactions · 31 stateful · 2026-09-22 05:29:50 UTC
Parallelism
80/100
Blocked
58%
Avg conflicts / tx
1.34
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,952,071 · 35 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
1w02w13w24w36w17w19w415w116w217w118w219w320w325w427w428w529w633w334w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x462c83cd…0d21
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002d
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xea2d3331…6e36
0x1b6862…e19c
8 touches
6 conflicts
0x34a5dca8…326a
0x34b655…2a6f
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
21 conflicts on slot 0x462c83cd38…da0d21
Audit this contract →
← previous block·next block →recent activity