← previous blocknext block →recent activity
Analyzing
Block #106,223,943
31 transactions · 25 stateful · 2026-09-19 16:24:08 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,223,943 · 31 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
1w02w13w24w35w09w010w116w118w219w320w421w124w425w530w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ab5df5c…3ac8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x638cd0f2…cb93
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0xe5060fe3…ebea
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 0x9ab5df5cb9…d73ac8
Audit this contract →
← previous block·next block →recent activity