← previous blocknext block →recent activity
Analyzing
Block #102,528,928
16 transactions · 12 stateful · 2026-09-06 17:32:30 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,528,928 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w011w112w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e0b06d1…5f32
0x34b655…2a6f
6 touches
3 conflicts
0x20b94f7c…2a9b
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 touches
1 conflict
0x4dffc33e…068d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x61db87ec…64ce
0x34b655…2a6f
4 touches
1 conflict
0x66d0c4a4…add3
0x34b655…2a6f
4 touches
1 conflict
0x67043b0b…97d7
0x34b655…2a6f
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 0x8e0b06d13d…d75f32
Audit this contract →
← previous block·next block →recent activity