← previous blocknext block →recent activity
Analyzing
Block #102,411,676
29 transactions · 26 stateful · 2026-09-06 07:38:08 UTC
Parallelism
76/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,411,676 · 29 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w09w112w315w417w119w421w224w325w426w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22f10271…841d
0x34b655…2a6f
10 touches
10 conflicts
0xc1508c42…efd7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x73912233…4585
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
10 conflicts on slot 0x22f10271ce…96841d
Audit this contract →
← previous block·next block →recent activity