← previous blocknext block →recent activity
Analyzing
Block #100,155,747
21 transactions · 14 stateful · 2026-08-29 10:04:36 UTC
Parallelism
86/100
Blocked
29%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,155,747 · 21 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
3w05w06w112w113w214w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
4 touches
1 conflict
0x4ec4cfad…6e4f
0xd32edf…ff58
3 touches
1 conflict
0x49cf54ec…b3e2
0x065c9d…c394
2 touches
0 conflicts
0xab2f6eed…254a
0x188d58…ea8e
2 touches
0 conflicts
0xab2f6eed…254c
0x188d58…ea8e
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity