← previous blocknext block →recent activity
Analyzing
Block #101,492,624
50 transactions · 34 stateful · 2026-09-03 02:15:08 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,492,624 · 50 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
2w06w112w018w019w121w022w124w127w234w240w041w246w347w449w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x9dead30b…7fde
0xd32edf…ff58
5 touches
3 conflicts
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x5aed1bd2…7afa
0x34b655…2a6f
4 touches
1 conflict
0x67bb9ccf…5da9
0x34b655…2a6f
4 touches
1 conflict
0x6dedaff6…161b
0x34b655…2a6f
4 touches
1 conflict
0x7b6d2deb…dde0
0x34b655…2a6f
4 touches
1 conflict
0x94dabb65…43a3
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity