← previous blocknext block →recent activity
Analyzing
Block #100,611,458
18 transactions · 16 stateful · 2026-08-31 00:21:20 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,611,458 · 18 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
1w02w03w14w211w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x8649e48f…941c
0xc8689a…ee79
6 touches
3 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2b41f02c…660e
0x065c9d…c394
2 touches
0 conflicts
0x360d61a1…b0ca
0x065c9d…c394
2 touches
0 conflicts
0x5390415a…185a
0x065c9d…c394
2 touches
0 conflicts
0x7e805ca1…0b72
0x065c9d…c394
2 touches
0 conflicts
0x8e61d81f…f3fb
0x065c9d…c394
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