← previous blocknext block →recent activity
Analyzing
Block #101,663,648
26 transactions · 25 stateful · 2026-09-03 16:35:30 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,663,648 · 26 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
1w02w13w04w15w06w111w012w113w214w218w021w223w024w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x9b4f173c…94e6
0x34b655…2a6f
6 touches
3 conflicts
0x02afcd2e…3f9c
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x000bde1a…e123
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity