← previous blocknext block →recent activity
Analyzing
Block #98,848,977
24 transactions · 18 stateful · 2026-08-24 20:06:50 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.29
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,848,977 · 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
2w09w010w111w213w117w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcf3283ba…c9fa
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x1e63ecbc…5e9c
0x065c9d…c394
3 touches
1 conflict
0x99e77f82…f3ef
0x065c9d…c394
3 touches
1 conflict
0x00000000…0004
0x023eb9…b2b4
2 touches
0 conflicts
0x00000000…0009
0x023eb9…b2b4
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: MarginAccount
3 conflicts on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity