← previous blocknext block →recent activity
Analyzing
Block #99,209,713
27 transactions · 21 stateful · 2026-08-26 02:28:26 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #99,209,713 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w17w28w39w010w116w217w320w021w122w425w026w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xba38536d…2b7d
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x5e65871a…cf98
0x065c9d…c394
4 touches
1 conflict
0x8451771e…320a
0x065c9d…c394
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity