← previous blocknext block →recent activity
Analyzing
Block #102,215,962
25 transactions · 24 stateful · 2026-09-05 15:06:35 UTC
Parallelism
72/100
Blocked
42%
Avg conflicts / tx
1.04
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #102,215,962 · 25 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
1w02w13w24w35w09w010w212w315w416w017w519w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe108b282…58b3
0x34b655…2a6f
10 touches
10 conflicts
0xd2fa90b4…0814
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x1f8a126c…9aa8
0x1b6862…e19c
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
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 0xe108b28272…6558b3
Audit this contract →
← previous block·next block →recent activity