← previous blocknext block →recent activity
Analyzing
Block #100,920,403
28 transactions · 23 stateful · 2026-09-01 02:15:49 UTC
Parallelism
86/100
Blocked
57%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,920,403 · 28 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
1w03w14w15w06w17w18w29w310w011w113w114w215w016w119w020w121w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b438c26…560f
0x065c9d…c394
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3f2100d8…f9b5
0xa6afd3…d132
6 touches
3 conflicts
0xc2aacf41…5502
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: Market-MON/USDC
3 conflicts on slot 0x9b438c26ad…21560f
Audit this contract →
← previous block·next block →recent activity