← previous blocknext block →recent activity
Analyzing
Block #99,239,997
16 transactions · 14 stateful · 2026-08-26 05:00:49 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,239,997 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x3f2100d8…f9b5
0xa6afd3…d132
4 touches
1 conflict
0xa366dc41…b2d8
0xa6afd3…d132
4 touches
1 conflict
0x35773bc2…716b
0x34b655…2a6f
2 touches
0 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
2 touches
0 conflicts
0x55010ec8…ea31
0x34b655…2a6f
2 touches
0 conflicts
0x5a27cf34…ae3b
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: MarginAccount
1 conflict on slot 0x889d5e90c7…59929a
Audit this contract →
← previous block·next block →recent activity