← previous blocknext block →recent activity
Analyzing
Block #100,699,111
25 transactions · 17 stateful · 2026-08-31 07:42:14 UTC
Parallelism
84/100
Blocked
53%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,699,111 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w27w012w013w117w218w319w220w321w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00f6a8a7…0e6e
0x34b655…2a6f
8 touches
6 conflicts
0x7f7fb616…f7d8
0x34b655…2a6f
8 touches
6 conflicts
0xcca1713b…033f
0xd32edf…ff58
7 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xdb8b3f25…e5db
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x6d43ee99…bdd3
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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 0x00f6a8a766…070e6e
Audit this contract →
← previous block·next block →recent activity