← previous blocknext block →recent activity
Analyzing
Block #100,619,398
26 transactions · 25 stateful · 2026-08-31 01:01:16 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,619,398 · 26 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
1w02w13w24w28w19w210w311w014w315w416w519w020w124w025w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05086df1…bd5a
0x34b655…2a6f
10 touches
10 conflicts
0xa6d40b7f…2969
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x37699b20…1076
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x05086df1aa…d7bd5a
Audit this contract →
← previous block·next block →recent activity