← previous blocknext block →recent activity
Analyzing
Block #100,111,573
26 transactions · 21 stateful · 2026-08-29 06:22:03 UTC
Parallelism
81/100
Blocked
57%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,111,573 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w08w09w110w112w015w217w119w220w321w322w124w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0148c30a…38e0
0x34b655…2a6f
8 touches
6 conflicts
0xc0f1c07b…ad7a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x172b0de5…980b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x0476d77b…a514
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
6 conflicts on slot 0x0148c30a22…e838e0
Audit this contract →
← previous block·next block →recent activity