← previous blocknext block →recent activity
Analyzing
Block #105,435,622
20 transactions · 17 stateful · 2026-09-16 22:14:04 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,435,622 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w27w38w09w113w314w016w417w418w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x849f2d32…5f99
0x34b655…2a6f
8 touches
6 conflicts
0x1296f4c3…64db
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd25997d0…a68a
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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 0x849f2d3291…d95f99
Audit this contract →
← previous block·next block →recent activity