← previous blocknext block →recent activity
Analyzing
Block #102,406,925
34 transactions · 26 stateful · 2026-09-06 07:14:05 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.71
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,406,925 · 34 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
1w02w13w24w37w08w09w111w122w023w424w125w227w030w231w332w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb3572c95…9c4a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb31eb7d3…64eb
0xa6afd3…d132
6 touches
3 conflicts
0x6a9e408e…3721
0x34b655…2a6f
6 touches
3 conflicts
0xdc38e55d…99d7
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x9b334941…fddd
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity