← previous blocknext block →recent activity
Analyzing
Block #99,876,020
26 transactions · 24 stateful · 2026-08-28 10:35:40 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #99,876,020 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w28w09w310w411w012w013w114w117w118w519w321w422w524w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x443a3e47…f4a4
0x065c9d…c394
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
10 touches
10 conflicts
0x6445cc9d…49a1
0x065c9d…c394
8 touches
6 conflicts
0xec10eada…9ecc
0x065c9d…c394
7 touches
6 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x06e40499…165e
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity