← previous blocknext block →recent activity
Analyzing
Block #100,868,713
28 transactions · 27 stateful · 2026-08-31 21:55:49 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #100,868,713 · 28 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
1w02w13w24w08w09w115w016w118w220w021w122w223w324w126w127w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47f06cc1…528c
0x065c9d…c394
9 touches
10 conflicts
0x002fed35…79fa
0x2a68ba…90c5
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a84f
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
10 conflicts on slot 0x47f06cc109…34528c
Audit this contract →
← previous block·next block →recent activity