← previous blocknext block →recent activity
Analyzing
Block #99,204,928
21 transactions · 16 stateful · 2026-08-26 02:04:22 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #99,204,928 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w17w08w29w110w112w013w115w316w217w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa674697c…b963
0x065c9d…c394
5 touches
3 conflicts
0x2e35df40…f5e4
0x34b655…2a6f
4 touches
1 conflict
0x3745e896…e102
0x34b655…2a6f
4 touches
1 conflict
0x631b4113…baa9
0x34b655…2a6f
4 touches
1 conflict
0x68c07cb9…ae14
0x34b655…2a6f
4 touches
1 conflict
0x98834cc0…6c23
0x34b655…2a6f
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
6 conflicts on slot 0x1125877469…519892
Audit this contract →
← previous block·next block →recent activity