← previous blocknext block →recent activity
Analyzing
Block #100,609,589
50 transactions · 44 stateful · 2026-08-31 00:11:56 UTC
Parallelism
80/100
Blocked
68%
Avg conflicts / tx
1.98
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #100,609,589 · 50 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w114w615w718w823w528w629w731w832w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0xe4f6e7…9657
16 touches
28 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
16 touches
28 conflicts
0x00000000…0008
0x0ea966…0742
16 touches
28 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
16 touches
28 conflicts
0x0fe6e5cd…f92d
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x580c6fe7…0fe9
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 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: 0xe4f6e757…919657
28 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity