← previous blocknext block →recent activity
Analyzing
Block #101,136,011
28 transactions · 27 stateful · 2026-09-01 20:20:51 UTC
Parallelism
75/100
Blocked
67%
Avg conflicts / tx
1.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,136,011 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w08w511w518w619w220w624w225w326w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xf5b5f7…6d70
12 touches
15 conflicts
0x5234c9d5…7859
0xd32edf…ff58
11 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c0
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 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: 0xf5b5f7f8…a36d70
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity