← previous blocknext block →recent activity
Analyzing
Block #106,916,875
20 transactions · 20 stateful · 2026-09-22 02:32:40 UTC
Parallelism
75/100
Blocked
35%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,916,875 · 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
1w02w13w24w06w07w18w19w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11ef1387…5a43
0x34b655…2a6f
10 touches
10 conflicts
0xf7b76d2f…1b9c
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 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
0xf58eca50…59fb
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
10 conflicts on slot 0x11ef13878d…995a43
Audit this contract →
← previous block·next block →recent activity