← previous blocknext block →recent activity
Analyzing
Block #100,565,106
34 transactions · 26 stateful · 2026-08-30 20:28:09 UTC
Parallelism
82/100
Blocked
46%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,565,106 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w110w212w014w015w016w119w221w324w025w126w327w428w532w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xba38536d…2b7d
0x065c9d…c394
10 touches
10 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0x348fda08…7e96
0x065c9d…c394
8 touches
6 conflicts
0xbb97db90…4c93
0xc8689a…ee79
6 touches
3 conflicts
0x06e40499…165e
0x2b46c0…1669
6 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
6 touches
3 conflicts
0xf6cc7de8…0b4a
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-MON/USDC
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity