← previous blocknext block →recent activity
Analyzing
Block #100,610,013
22 transactions · 19 stateful · 2026-08-31 00:14:04 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.41
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,610,013 · 22 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
1w03w05w06w18w09w111w113w214w015w116w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68106229…7057
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…0000
0x019883…2a9a
6 touches
3 conflicts
0x00000000…0002
0x019883…2a9a
6 touches
3 conflicts
0xa10c86f8…4b74
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0003
0x019883…2a9a
6 touches
3 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
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-WETH/USDC
3 conflicts on slot 0x68106229be…ec7057
Audit this contract →
← previous block·next block →recent activity