← previous blocknext block →recent activity
Analyzing
Block #100,875,504
33 transactions · 29 stateful · 2026-08-31 22:29:59 UTC
Parallelism
64/100
Blocked
66%
Avg conflicts / tx
2.3
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #100,875,504 · 33 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w36w37w48w510w611w712w818w123w224w925w926w1027w1129w132w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
20 touches
45 conflicts
0x892daf6e…48d8
0x065c9d…c394
18 touches
36 conflicts
0xaad6be10…0801
0x2a68ba…90c5
12 touches
15 conflicts
0x06e40499…165e
0x34ae4d…3fc5
12 touches
15 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
12 touches
15 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
12 touches
15 conflicts
0x65f770b2…ba36
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 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: Kuru Exchange: Market-MON/USDC
45 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity