← previous blocknext block →recent activity
Analyzing
Block #106,931,434
23 transactions · 23 stateful · 2026-09-22 03:45:57 UTC
Parallelism
74/100
Blocked
57%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,931,434 · 23 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
1w02w13w04w15w27w28w39w010w113w114w315w216w417w418w521w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8727c567…8832
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xc8c615d4…5da3
0x34b655…2a6f
6 touches
3 conflicts
0xd125c3f8…99aa
0x34b655…2a6f
6 touches
3 conflicts
0x6c26d635…1bbf
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0x8727c56764…828832
Audit this contract →
← previous block·next block →recent activity