← previous blocknext block →recent activity
Analyzing
Block #98,751,220
21 transactions · 17 stateful · 2026-08-24 11:54:40 UTC
Parallelism
86/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #98,751,220 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w011w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xc4e19ae4…0788
0xe7cd86…c82d
4 touches
1 conflict
0x0f8965bb…e238
0x34b655…2a6f
2 touches
0 conflicts
0x306a45c3…3224
0x34b655…2a6f
2 touches
0 conflicts
0x58e8bb59…8306
0x34b655…2a6f
2 touches
0 conflicts
0x918415c4…e9d1
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity