← previous blocknext block →recent activity
Analyzing
Block #98,391,451
24 transactions · 21 stateful · 2026-08-23 05:08:26 UTC
Parallelism
79/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,391,451 · 24 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
1w02w13w04w211w314w415w018w020w122w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x2620cf4d…3956
0x065c9d…c394
5 touches
3 conflicts
0x0915c291…c364
0x065c9d…c394
5 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0000
0x094452…0a09
4 touches
1 conflict
0x00000000…0003
0x094452…0a09
4 touches
1 conflict
0x00000000…0004
0x094452…0a09
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
10 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity