← previous blocknext block →recent activity
Analyzing
Block #101,502,763
17 transactions · 14 stateful · 2026-09-03 03:06:09 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,502,763 · 17 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
1w02w13w24w310w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x42ab2fcf…1e1c
0xd32edf…ff58
5 touches
3 conflicts
0x6636a104…d595
0x34b655…2a6f
4 touches
1 conflict
0x514a514b…93d7
0x34b655…2a6f
4 touches
1 conflict
0x9a9383a9…6bc7
0x34b655…2a6f
4 touches
1 conflict
0xa57a72ed…64c2
0x34b655…2a6f
4 touches
1 conflict
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity