← previous blocknext block →recent activity
Analyzing
Block #100,699,731
19 transactions · 17 stateful · 2026-08-31 07:45:21 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,699,731 · 19 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
2w03w14w06w07w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x163bae78…bb42
0x065c9d…c394
3 touches
1 conflict
0xc1fff17d…e57d
0x754704…b603
2 touches
0 conflicts
0xc66cceb7…af6e
0x754704…b603
2 touches
0 conflicts
0xd4a53e1e…b679
0x754704…b603
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 0x5f77d60791…b12c84
Audit this contract →
← previous block·next block →recent activity