← previous blocknext block →recent activity
Analyzing
Block #100,140,531
31 transactions · 26 stateful · 2026-08-29 08:48:00 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,140,531 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w19w316w018w120w221w422w325w326w427w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xc08263f8…4460
0x065c9d…c394
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xc6a0aea7…a426
0x34b655…2a6f
8 touches
6 conflicts
0x45f562b2…9294
0x2b46c0…1669
6 touches
3 conflicts
0x8488f10f…9353
0x2b46c0…1669
6 touches
3 conflicts
0x8488f10f…9354
0x2b46c0…1669
6 touches
3 conflicts
0xa605468c…1bfc
0x2b46c0…1669
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity