← previous blocknext block →recent activity
Analyzing
Block #99,699,852
17 transactions · 15 stateful · 2026-08-27 19:44:06 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,699,852 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w010w113w214w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79c1f55f…d4ca
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0xf874c89c…239c
0xd32edf…ff58
5 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a996
0x188d58…ea8e
2 touches
0 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
3 conflicts on slot 0x79c1f55fa9…80d4ca
Audit this contract →
← previous block·next block →recent activity