← previous blocknext block →recent activity
Analyzing
Block #101,937,953
33 transactions · 30 stateful · 2026-09-04 15:37:16 UTC
Parallelism
79/100
Blocked
53%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,937,953 · 33 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
1w02w13w24w35w46w57w69w011w113w214w332w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8bf661cb…bcd2
0x34b655…2a6f
12 touches
15 conflicts
0xa1a01ded…c087
0x34b655…2a6f
12 touches
15 conflicts
0xd98afa6e…3364
0x34b655…2a6f
12 touches
15 conflicts
0x93aaefce…5be5
0x34b655…2a6f
12 touches
15 conflicts
0x29a58269…011a
0x34b655…2a6f
12 touches
15 conflicts
0xb47d4bdd…6172
0x34b655…2a6f
12 touches
15 conflicts
0x987859be…2686
0x34b655…2a6f
10 touches
10 conflicts
0x7fd951f1…fe49
0x34b655…2a6f
10 touches
10 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
15 conflicts on slot 0x8bf661cb38…d4bcd2
Audit this contract →
← previous block·next block →recent activity