← previous blocknext block →recent activity
Analyzing
Block #100,809,350
20 transactions · 20 stateful · 2026-08-31 16:57:00 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,809,350 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w06w17w216w117w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03cabc68…bc3b
0x34b655…2a6f
2 touches
0 conflicts
0x340f8b07…7ec4
0x34b655…2a6f
2 touches
0 conflicts
0x3861b165…8482
0x34b655…2a6f
2 touches
0 conflicts
0x54907f2c…4a40
0x34b655…2a6f
2 touches
0 conflicts
0x56fe17b8…39b1
0x34b655…2a6f
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity