← previous blocknext block →recent activity
Analyzing
Block #102,219,065
28 transactions · 27 stateful · 2026-09-05 15:22:14 UTC
Parallelism
71/100
Blocked
59%
Avg conflicts / tx
1.29
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,219,065 · 28 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w18w19w210w211w315w016w117w218w321w422w523w524w627w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x256918f1…c4d0
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x0a85a226…83c1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x93109a16…4f3e
0x34b655…2a6f
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
10 conflicts on slot 0x256918f186…59c4d0
Audit this contract →
← previous block·next block →recent activity