← previous blocknext block →recent activity
Analyzing
Block #98,461,215
16 transactions · 13 stateful · 2026-08-23 10:59:41 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,461,215 · 16 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
1w03w14w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b807a2…3307
0x065c9d…c394
6 touches
3 conflicts
0x11258774…9892
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xb5f359a0…96d2
0x065c9d…c394
5 touches
3 conflicts
0x065c4b5b…b18d
0x065c9d…c394
4 touches
2 conflicts
0x50e40524…51a0
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x47b807a243…c53307
Audit this contract →
← previous block·next block →recent activity