← previous blocknext block →recent activity
Analyzing
Block #102,152,126
24 transactions · 24 stateful · 2026-09-05 09:43:02 UTC
Parallelism
58/100
Blocked
54%
Avg conflicts / tx
1.21
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #102,152,126 · 24 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w37w49w510w612w013w114w717w819w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe45073e…6315
0x34b655…2a6f
12 touches
15 conflicts
0x11e5dc13…c0cc
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x14d1bf0e…e09e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0xfe45073ed9…0c6315
Audit this contract →
← previous block·next block →recent activity