← previous blocknext block →recent activity
Analyzing
Block #100,585,171
22 transactions · 21 stateful · 2026-08-30 22:09:05 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.41
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,585,171 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w48w59w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0xba38536d…2b7d
0x065c9d…c394
14 touches
21 conflicts
0x06e40499…165e
0x2b46c0…1669
14 touches
21 conflicts
0xbb97db90…4c93
0xc8689a…ee79
14 touches
21 conflicts
0x11258774…9892
0x2a68ba…90c5
12 touches
15 conflicts
0x348fda08…7e96
0x065c9d…c394
12 touches
15 conflicts
0xa605468c…1bfc
0x2b46c0…1669
11 touches
15 conflicts
0x8488f10f…9353
0x2b46c0…1669
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: Kuru Exchange: Market-MON/USDC
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity