← previous blocknext block →recent activity
Analyzing
Block #99,252,129
13 transactions · 12 stateful · 2026-08-26 06:01:51 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,252,129 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w07w19w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd1da92c…14bc
0x065c9d…c394
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x8b2b7213…4899
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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
1 conflict on slot 0xdd1da92c14…2e14bc
Audit this contract →
← previous block·next block →recent activity