← previous blocknext block →recent activity
Analyzing
Block #100,565,421
31 transactions · 26 stateful · 2026-08-30 20:29:44 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.61
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,565,421 · 31 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
1w02w13w05w17w08w19w013w014w115w216w319w420w222w023w525w126w227w130w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x33000c0a…82c3
0x34b655…2a6f
8 touches
6 conflicts
0x0490581d…adaf
0x34b655…2a6f
6 touches
3 conflicts
0xa4f89034…6931
0x34b655…2a6f
6 touches
3 conflicts
0xb08f0c78…122e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xe01158fd…f982
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 0x33000c0a30…f582c3
Audit this contract →
← previous block·next block →recent activity