← previous blocknext block →recent activity
Analyzing
Block #100,093,458
15 transactions · 15 stateful · 2026-08-29 04:50:51 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,093,458 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x02bb59aa…e49b
0x065c9d…c394
2 touches
0 conflicts
0x1364ed42…6866
0x065c9d…c394
2 touches
0 conflicts
0x1f7def57…a428
0x065c9d…c394
2 touches
0 conflicts
0x59bd3861…6e29
0x065c9d…c394
2 touches
0 conflicts
0x89077196…e045
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity