← previous blocknext block →recent activity
Analyzing
Block #102,325,981
24 transactions · 24 stateful · 2026-09-06 00:24:01 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,325,981 · 24 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w09w110w214w015w116w218w320w321w422w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x762b0e58…1cc0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x2e1f5171…ad2d
0x34b655…2a6f
8 touches
6 conflicts
0x42e5184f…4e8b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xbceecf11…0120
0x34b655…2a6f
8 touches
6 conflicts
0xaceaf2ae…52e8
0x34b655…2a6f
7 touches
6 conflicts
0xd9f18d9a…141d
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
6 conflicts on slot 0x762b0e5885…221cc0
Audit this contract →
← previous block·next block →recent activity