← previous blocknext block →recent activity
Analyzing
Block #101,022,706
21 transactions · 19 stateful · 2026-09-01 10:50:30 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,022,706 · 21 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
1w02w14w08w19w210w311w413w115w518w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1408a100…f721
0x34b655…2a6f
10 touches
10 conflicts
0x21fdc4c7…9964
0x34b655…2a6f
10 touches
10 conflicts
0x29cd05f5…390c
0x34b655…2a6f
10 touches
10 conflicts
0x4f850ac3…1670
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x1408a100e8…d7f721
Audit this contract →
← previous block·next block →recent activity