← previous blocknext block →recent activity
Analyzing
Block #108,971,971
22 transactions · 19 stateful · 2026-09-29 07:03:56 UTC
Parallelism
73/100
Blocked
63%
Avg conflicts / tx
1.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,971,971 · 22 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
1w02w13w24w35w47w08w19w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1e17087…5fb1
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x69017fce…85c1
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0xb70ea60e…0723
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0057
0x1b6862…e19c
8 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
15 conflicts on slot 0xe1e170875b…ec5fb1
Audit this contract →
← previous block·next block →recent activity