← previous blocknext block →recent activity
Analyzing
Block #100,918,493
26 transactions · 24 stateful · 2026-09-01 02:06:12 UTC
Parallelism
81/100
Blocked
46%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,918,493 · 26 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
1w03w04w15w16w011w212w314w316w017w118w219w320w422w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x64add51a…dd96
0x065c9d…c394
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
10 touches
10 conflicts
0x35637a40…afe5
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0x6aa624fd…a850
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x64add51a7d…4ddd96
Audit this contract →
← previous block·next block →recent activity