← previous blocknext block →recent activity
Analyzing
Block #107,815,658
17 transactions · 16 stateful · 2026-09-25 05:59:01 UTC
Parallelism
71/100
Blocked
44%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,815,658 · 17 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
1w02w13w24w39w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc844ab5…4c6d
0x34b655…2a6f
10 touches
10 conflicts
0x232b0b19…d946
0x34b655…2a6f
10 touches
10 conflicts
0x3c670f07…2b71
0x34b655…2a6f
10 touches
10 conflicts
0x5cf4d55d…c588
0x34b655…2a6f
10 touches
10 conflicts
0xba5743c7…21c6
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xaf4988d9…48ea
0xd32edf…ff58
7 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
10 conflicts on slot 0xcc844ab542…814c6d
Audit this contract →
← previous block·next block →recent activity