← previous blocknext block →recent activity
Analyzing
Block #108,512,170
29 transactions · 28 stateful · 2026-09-27 16:24:34 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,512,170 · 29 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
1w02w13w24w39w010w212w013w014w315w121w423w424w525w126w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19dcf812…44d9
0x34b655…2a6f
8 touches
6 conflicts
0xb5deb941…0780
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x0a6cb118…4ca8
0x1b6862…e19c
6 touches
3 conflicts
0x28e83c04…0481
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0x19dcf812b9…df44d9
Audit this contract →
← previous block·next block →recent activity