← previous blocknext block →recent activity
Analyzing
Block #99,953,679
34 transactions · 31 stateful · 2026-08-28 17:07:03 UTC
Parallelism
71/100
Blocked
65%
Avg conflicts / tx
1.94
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #99,953,679 · 34 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w37w48w510w624w129w730w831w932w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x5f77d607…2c84
0x065c9d…c394
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…0002
0xf5b5f7…6d70
14 touches
21 conflicts
0xa605468c…1bfc
0x2b46c0…1669
10 touches
10 conflicts
0xbb97db90…4c93
0xc8689a…ee79
10 touches
10 conflicts
0x06e40499…165e
0x2b46c0…1669
10 touches
10 conflicts
0x0362c4c5…0168
0x065c9d…c394
8 touches
6 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity