← previous blocknext block →recent activity
Analyzing
Block #100,923,476
18 transactions · 17 stateful · 2026-09-01 02:31:16 UTC
Parallelism
67/100
Blocked
59%
Avg conflicts / tx
1.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,923,476 · 18 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
1w02w13w14w26w17w28w39w410w511w317w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
12 touches
15 conflicts
0xa1087a5c…66c4
0x754704…b603
10 touches
10 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0x62f8f400…4518
0x065c9d…c394
8 touches
6 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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: MarginAccount
15 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity