← previous blocknext block →recent activity
Analyzing
Block #101,149,728
18 transactions · 14 stateful · 2026-09-01 21:29:51 UTC
Parallelism
83/100
Blocked
36%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,149,728 · 18 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
1w02w14w05w113w014w115w216w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68e5627d…6f8f
0x34b655…2a6f
6 touches
3 conflicts
0x2876a9e0…19c8
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf476c3f2…a733
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
2 touches
0 conflicts
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 0x68e5627d66…486f8f
Audit this contract →
← previous block·next block →recent activity