← previous blocknext block →recent activity
Analyzing
Block #102,528,519
14 transactions · 14 stateful · 2026-09-06 17:30:26 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,528,519 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w39w411w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6b208b1f…4159
0x34b655…2a6f
6 touches
3 conflicts
0x359866c7…de7b
0x34b655…2a6f
6 touches
3 conflicts
0xa1d3b7c9…266f
0xd32edf…ff58
5 touches
3 conflicts
0xe2263bea…6aa0
0x34ae4d…3fc5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xe2263bea…6a9d
0x34ae4d…3fc5
4 touches
1 conflict
0xe2263bea…6a9e
0x34ae4d…3fc5
4 touches
1 conflict
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
3 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity